[jira] Commented: (MNG-870) Make plugin discovery reactor aware
[ http://jira.codehaus.org/browse/MNG-870?page=comments#action_80983 ] Kenney Westerhof commented on MNG-870: -- Hm, stupid jira.. ;) I've created a new issue at MNG-2677. Make plugin discovery reactor aware --- Key: MNG-870 URL: http://jira.codehaus.org/browse/MNG-870 Project: Maven 2 Issue Type: New Feature Components: Plugins and Lifecycle Reporter: Kenney Westerhof Assigned To: Brett Porter Fix For: 2.0-beta-2 Attachments: MNG-870.diff Original Estimate: 1 hour Time Spent: 1 hour Remaining Estimate: 0 minutes If plugin discovery is reactor aware, plugins that are part of a reactor build and are used to aid the build can be used in one go. Else first the plugin should be installed, and then the rest of the project can be built. But mainly this aids in integration testing for plugins: the maven-it-plugin in sandbox can't add the current plugin + artifact to the lifecycle without making some methods public. If the plugin were to be discovered using the reactor, those methods can remain private. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-870) Make plugin discovery reactor aware
[ http://jira.codehaus.org/browse/MNG-870?page=comments#action_77452 ] Kenney Westerhof commented on MNG-870: -- It fails currently. Another IT test probably installed a test:test-plugin (81?); after making the artifactId unique (it0042-test-plugin) it fails. Make plugin discovery reactor aware --- Key: MNG-870 URL: http://jira.codehaus.org/browse/MNG-870 Project: Maven 2 Issue Type: New Feature Components: Plugins and Lifecycle Reporter: Kenney Westerhof Assigned To: Brett Porter Fix For: 2.0-beta-2 Attachments: MNG-870.diff Original Estimate: 1 hour Time Spent: 1 hour Remaining Estimate: 0 minutes If plugin discovery is reactor aware, plugins that are part of a reactor build and are used to aid the build can be used in one go. Else first the plugin should be installed, and then the rest of the project can be built. But mainly this aids in integration testing for plugins: the maven-it-plugin in sandbox can't add the current plugin + artifact to the lifecycle without making some methods public. If the plugin were to be discovered using the reactor, those methods can remain private. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-870) Make plugin discovery reactor aware
[ http://jira.codehaus.org/browse/MNG-870?page=comments#action_77468 ] Kenney Westerhof commented on MNG-870: -- It's affected by this: it0042, it0096 and it0097. Make plugin discovery reactor aware --- Key: MNG-870 URL: http://jira.codehaus.org/browse/MNG-870 Project: Maven 2 Issue Type: New Feature Components: Plugins and Lifecycle Reporter: Kenney Westerhof Assigned To: Brett Porter Fix For: 2.0-beta-2 Attachments: MNG-870.diff Original Estimate: 1 hour Time Spent: 1 hour Remaining Estimate: 0 minutes If plugin discovery is reactor aware, plugins that are part of a reactor build and are used to aid the build can be used in one go. Else first the plugin should be installed, and then the rest of the project can be built. But mainly this aids in integration testing for plugins: the maven-it-plugin in sandbox can't add the current plugin + artifact to the lifecycle without making some methods public. If the plugin were to be discovered using the reactor, those methods can remain private. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
