Looks like the 1.1 version of the shade plugin didn't do what I needed it to WRT avoiding rewriting the Xpp3Dom and/or XmlSerializer classes. The IT for MNG-3503 is messed up in the RC1 build, so I'll be cutting an RC2 as soon as I can verify that 1.0 of the shade plugin works (this is what we used in 2.0.9, with no problems).

I rolled this plugin version back from 1.2-SNAPSHOT, so I assume that 1.1 contains a regression? I guess I should've done the leg work to make sure the behavior I needed hadn't changed...

I'll let everyone know as soon as I have an RC2 ready. The most notable place this error is going to strike is when installing a POM-packaging project that has a site descriptor in its src/site directory...

-john

John Casey wrote:
Hi again,

As promised, I've staged the first release candidate for Maven 2.0.10 here:

http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/

The issues resolved for this release (so far) are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112

If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is still open. This is because one of the possible solutions to this issue - and the only one that the Maven project really has control over - depends on re-releasing a new version of commons-build-plugin that will depend on the eventual 2.0.10 version of maven-script-ant.

Please, try out this release candidate and let me know what's broken! Once things stabilize, I'll kick it out to the users to have a go, then if it's still stable after that (or, whatever RC we find is stable at that point), I'll call a vote to release. At that point, I'll run a new build to generate artifacts without the RC# suffix in the version.

Thanks!

-john


--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to