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/07/17 02:29:57 UTC
[jira] Created: (MNG-598) new type handlers cannot be added outside of maven-core
new type handlers cannot be added outside of maven-core
-------------------------------------------------------
Key: MNG-598
URL: http://jira.codehaus.org/browse/MNG-598
Project: Maven 2
Type: Bug
Reporter: Brett Porter
Fix For: 2.0-beta-1
adding type handlers in your own plugin will not put them into the map that the lifecycle executor is using. the maps need to be merged.
--
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] Commented: (MNG-598) new type handlers cannot be added outside of maven-core
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-598?page=comments#action_43356 ]
Brett Porter commented on MNG-598:
----------------------------------
We don't want to have to resolve and search all
the plugins to find a missing dependency type. For this, we can add
<extensions>true|false</extensions> to the <plugin/> element, eg:
<plugin>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
...
</configuration>
</plugin>
This will indicate to the plugin manager to pre-load those plugins, and
to search it for any plexus components. When the lifecycle executor is
looking for a packaging handler, it will have to search those plugin
containers also.
> new type handlers cannot be added outside of maven-core
> -------------------------------------------------------
>
> Key: MNG-598
> URL: http://jira.codehaus.org/browse/MNG-598
> Project: Maven 2
> Type: Bug
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> adding type handlers in your own plugin will not put them into the map that the lifecycle executor is using. the maps need to be merged.
--
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] Commented: (MNG-598) new type handlers cannot be added outside of maven-core
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-598?page=comments#action_43448 ]
Brett Porter commented on MNG-598:
----------------------------------
packaging handlers are done (but that was the easy bit!)
> new type handlers cannot be added outside of maven-core
> -------------------------------------------------------
>
> Key: MNG-598
> URL: http://jira.codehaus.org/browse/MNG-598
> Project: Maven 2
> Type: Bug
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> adding type handlers in your own plugin will not put them into the map that the lifecycle executor is using. the maps need to be merged.
--
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-598) new type handlers cannot be added outside of maven-core
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-598?page=all ]
Brett Porter closed MNG-598:
----------------------------
Resolution: Fixed
the solution is a little hacky, might want to take another loook at it with the artifact refactoring
> new type handlers cannot be added outside of maven-core
> -------------------------------------------------------
>
> Key: MNG-598
> URL: http://jira.codehaus.org/browse/MNG-598
> Project: Maven 2
> Type: Bug
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> adding type handlers in your own plugin will not put them into the map that the lifecycle executor is using. the maps need to be merged.
--
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] Commented: (MNG-598) new type handlers cannot be added outside of maven-core
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-598?page=comments#action_43022 ]
Brett Porter commented on MNG-598:
----------------------------------
this is implemented for packaging, but there are problems:
- not implemented for type
- implementation currently uses plugins.xml which is per-user configured, which is a reproducibility problem
Needs to use the plugins defined in the POM for finding them, but this introduces more issues:
- is this too onerous for a dependency type definition?
- verifying all of the plugins in the POM before building is inefficient, so it would be good to be able to point directly to the plugin that has the packaging
> new type handlers cannot be added outside of maven-core
> -------------------------------------------------------
>
> Key: MNG-598
> URL: http://jira.codehaus.org/browse/MNG-598
> Project: Maven 2
> Type: Bug
> Reporter: Brett Porter
> Fix For: 2.0-beta-1
>
>
> adding type handlers in your own plugin will not put them into the map that the lifecycle executor is using. the maps need to be merged.
--
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] Updated: (MNG-598) new type handlers cannot be added outside of maven-core
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-598?page=all ]
Brett Porter updated MNG-598:
-----------------------------
Priority: Blocker (was: Major)
> new type handlers cannot be added outside of maven-core
> -------------------------------------------------------
>
> Key: MNG-598
> URL: http://jira.codehaus.org/browse/MNG-598
> Project: Maven 2
> Type: Bug
> Reporter: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> adding type handlers in your own plugin will not put them into the map that the lifecycle executor is using. the maps need to be merged.
--
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