You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/06/20 03:07:52 UTC
[jira] Created: (MNG-494) defer plugin dependency resolution to execution rather than at addPlugin
defer plugin dependency resolution to execution rather than at addPlugin
------------------------------------------------------------------------
Key: MNG-494
URL: http://jira.codehaus.org/browse/MNG-494
Project: Maven 2
Type: Improvement
Components: maven-core
Reporter: Brett Porter
Assigned to: John Casey
Fix For: 2.0-beta-1
because plugins are established at the start of the run, dependencies are all resolved at the start, even if some are never executed. This means getting dependencies of mojos you aren't even using. This is something to improve in the lifecycle executor, but it would still be good to defer plugin dep resolution until execution, the same as it is for the project itself. It would also mean not getting such a large dep hit at the start of a reactor build.
This would complicate the set up of the classworld, otherwise it would be a quick fix.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-494) defer plugin dependency resolution to execution rather than at addPlugin
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-494?page=all ]
Brett Porter closed MNG-494:
----------------------------
Resolution: Fixed
Fix Version: (was: 2.0-beta-1)
2.0-alpha-3
> defer plugin dependency resolution to execution rather than at addPlugin
> ------------------------------------------------------------------------
>
> Key: MNG-494
> URL: http://jira.codehaus.org/browse/MNG-494
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-alpha-3
>
>
> because plugins are established at the start of the run, dependencies are all resolved at the start, even if some are never executed. This means getting dependencies of mojos you aren't even using. This is something to improve in the lifecycle executor, but it would still be good to defer plugin dep resolution until execution, the same as it is for the project itself. It would also mean not getting such a large dep hit at the start of a reactor build.
> This would complicate the set up of the classworld, otherwise it would be a quick fix.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNG-494) defer plugin dependency resolution to execution rather than at addPlugin
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-494?page=all ]
Brett Porter reopened MNG-494:
------------------------------
reopen to fix version
> defer plugin dependency resolution to execution rather than at addPlugin
> ------------------------------------------------------------------------
>
> Key: MNG-494
> URL: http://jira.codehaus.org/browse/MNG-494
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-alpha-3
>
>
> because plugins are established at the start of the run, dependencies are all resolved at the start, even if some are never executed. This means getting dependencies of mojos you aren't even using. This is something to improve in the lifecycle executor, but it would still be good to defer plugin dep resolution until execution, the same as it is for the project itself. It would also mean not getting such a large dep hit at the start of a reactor build.
> This would complicate the set up of the classworld, otherwise it would be a quick fix.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-494) defer plugin dependency resolution to execution rather than at addPlugin
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-494?page=all ]
John Casey closed MNG-494:
--------------------------
Resolution: Fixed
> defer plugin dependency resolution to execution rather than at addPlugin
> ------------------------------------------------------------------------
>
> Key: MNG-494
> URL: http://jira.codehaus.org/browse/MNG-494
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
>
> because plugins are established at the start of the run, dependencies are all resolved at the start, even if some are never executed. This means getting dependencies of mojos you aren't even using. This is something to improve in the lifecycle executor, but it would still be good to defer plugin dep resolution until execution, the same as it is for the project itself. It would also mean not getting such a large dep hit at the start of a reactor build.
> This would complicate the set up of the classworld, otherwise it would be a quick fix.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org