You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/09/25 08:16:45 UTC
[jira] Created: (MNG-3766) toolchains not found in extensions
toolchains not found in extensions
----------------------------------
Key: MNG-3766
URL: http://jira.codehaus.org/browse/MNG-3766
Project: Maven 2
Issue Type: Bug
Components: Settings
Affects Versions: 2.1.0-M1, 2.0.9
Reporter: Brett Porter
There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Closed: (MNG-3766) toolchains not found in extensions
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-3766.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.0-beta-1)
3.0-alpha-3
Assignee: Benjamin Bentmann
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3766:
------------------------------
Assignee: Brett Porter
Fix Version/s: 2.0.10
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0.10
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3766:
------------------------------
Fix Version/s: (was: 2.3.x)
3.0-alpha-7
let's check if this works in 3.0's extension loading
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Fix For: 3.0-alpha-7
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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-3766) toolchains not found in extensions
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152062#action_152062 ]
John Casey commented on MNG-3766:
---------------------------------
As I documented here:
http://docs.codehaus.org/display/MAVEN/Maven+2.1+Plugin+and+Extension+Loading+Design
The extension-loading mechanism in maven 2.x is horrible, and prone to all sorts of weird behavioral changes depending on things like the number of artifacts in the extension's transitive dependency closure. IMO it needs to be replaced with something sensible. If we don't take the time to fix this mess, it's just going to extend the confusion surrounding extensions (which are problematic for a lot of users I've talked to) into the realm of toolchains as well.
I'm definitely -1 for patching the extension-loading code to support toolchains the same way wagons are supported now.
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0.10, 2.1.0-M2
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3766:
---------------------------
Fix Version/s: (was: 2.1.0-M2)
(was: 2.0.10)
2.0.11
We have a ton of issues in 2.0.10 with votes, lets bump this and move on with the release.
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0.11
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3766:
------------------------------
Assignee: (was: Brett Porter)
Fix Version/s: (was: 2.1.0)
2.2.0-M1
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Fix For: 2.2.0-M1
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-3766:
-------------------------------
Fix Version/s: 2.1.0-M2
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0.10, 2.1.0-M2
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3766:
------------------------------
Fix Version/s: (was: 2.1.0-M2)
2.1.0-M3
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.1.0-M3
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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] Updated: (MNG-3766) toolchains not found in extensions
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3766:
------------------------------
Fix Version/s: (was: 2.0.11)
2.1.0-M2
agreed. I'd originally intended this only for 2.1.0-M2, had just thought to investigate the impact of a potential fix before pulling the trigger on 2.0.10
> toolchains not found in extensions
> ----------------------------------
>
> Key: MNG-3766
> URL: http://jira.codehaus.org/browse/MNG-3766
> Project: Maven 2
> Issue Type: Bug
> Components: Settings
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.1.0-M2
>
>
> There's currently no way to plugin in new toolchains without placing them in M2_HOME/lib. For wagons to be available in extensions, the extension manager explicitly registers them - so I propose to do the same in 2.1.0-M2 for toolchains, and only support the Java toolchains in 2.0.9.
--
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