I've addressed Issue #3 below, and have uploaded a snapshot of the ant
tasks with dependencies bundle here:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/maven-artifact-ant/2.0.2-SNAPSHOT/
for testing.
Also, I've uploaded a snapshot of the new reporting-impl jar here:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/reporting/maven-reporting-impl/2.0.2-SNAPSHOT/
If all goes well with testing these and nothing else comes up, we'll
probably release 2.0.2 early next week.
Thanks,
John
John Casey wrote:
Hi everyone,
I wanted to take a second and let you know what we're working on to
address the major issues introduced by the 2.0.1 release. First, we're
planning an emergency 2.0.2 release to resolve the three or four
critical bugs that have surfaced. This release should be ready to go by
Monday at the latest, but we're going to take a little more time and
test it as thoroughly as we can before letting it go, particularly in
light of the last release. :-\
Ok, on to the specific issues:
1. Error parsing environment variables (Maven fails shortly after
starting execution) [MNG-1819]
This was an issue with newlines in the values of some environment
variables. Essentially, the parser we had assumed that each new line in
the buffer would represent a separate environment variable with
'key=value' syntax. Obviously, this was a terrible assumption to make.
We have corrected this in SVN (the project is plexus-utils, version is
1.0.6-SNAPSHOT), and will release it with 2.0.2 of Maven.
2. Some reports fail to run because they cannot lookup a component
called 'org.codehaus.doxia.site.renderer.SiteRenderer' [MNG-1834]
This was a result of changing the home of Doxia from codehaus to
maven/ASF. During this move, we changed the groupId (fine), and the
package names (not-so-fine). The change in package naming caused the
break in compatibility, and also the changed component name. This meant
that reports requesting that the SiteRenderer component to be injected
failed. Even if the component definition were there, the API differences
would have caused failure of these reports.
We have addressed this issue by implementing a very thin compatibility
layer between maven-reporting and the new doxia classes. This will allow
us to deprecate the old package names and eventually remove them. This
will also be released with 2.0.2.
3. "Duplicate project ID found" message when running the Maven Ant tasks
[MNG-1850/MNG-1851]
I'm not currently sure what the cause of this issue is. It's the next
one on the list, and the fix will be released with 2.0.2.
Sorry for the inconvenience,
John Casey
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
