You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stuart McCulloch (JIRA)" <ji...@codehaus.org> on 2013/03/13 02:38:52 UTC

[jira] (MNG-5453) Update Maven 3 build to use Eclipse/Sisu

Stuart McCulloch created MNG-5453:
-------------------------------------

             Summary: Update Maven 3 build to use Eclipse/Sisu
                 Key: MNG-5453
                 URL: https://jira.codehaus.org/browse/MNG-5453
             Project: Maven 2 & 3
          Issue Type: Task
          Components: Bootstrap & Build
            Reporter: Stuart McCulloch


Eclipse/Sisu is now able to run Maven3 (trunk) without requiring the legacy configurators bundled as part of the original Sisu build. These were the only classes that couldn't be moved to Eclipse as I wasn't 100% sure about their IP history.

Instead the 0.0.0.M2 milestone of Eclipse/Sisu includes new configurators written from scratch that build on Sisu's bean reflection/converter code. These new configurators were written (and tested) indirectly by looking at the behaviour of the old configurators while running various ITs, so it's possible that some inconsistencies remain.

So while the build passes all ITs locally, it would be worthwhile getting wider testing to make sure that I haven't accidentally regressed anything with the new configurator code :)

PS. the Eclipse/Sisu artifacts don't shade their internal dependencies (unlike the original Sisu bundles) so you'll see additional jars in lib, such as asm and guava. Also note that the guava dependency version is managed to be 11.0.2, which is the last known Java5 compatible release.

[patch will be sent via pull-request]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira