[ http://jira.codehaus.org/browse/MNG-377?page=all ]
John Casey updated MNG-377:
---------------------------
Description:
We have a default rule which will be used as a fallback, where the
prefix "idea" is turned into "maven-idea-plugin". This will be retained
if no other information is found.
Before applying the default rule, some more metadata from the repository
will be consulted. This will be stored at the group level, and named
"plugins.xml".
/org/apache/maven/plugins/plugins.xml
/org.apache.maven.plugins/plugins.xml
While this could potentially include version information as well, it is
worth being able to check these on a plugin-by-plugin basis, and it also
fits with the potential RELEASE specifier on dependencies. This could be
reconsidered in future versions.
Format of the file for now is simple:
<prefixes>
<groupId>org.apache.maven.plugins</groupId>
<plugins>
<plugin>
<prefix>idea</prefix>
<artifactId>maven-idea-plugin</artifactId>
</plugin>
...
</plugins>
</prefixes>
This particular file will also be updated at release time for a plugin
(though it should rarely be necessary as only new additions need to be
published back).
The list of group IDs to search will be configured from settings.xml,
with the default being just org.apache.maven.plugins. The process will
be to load the plugins.xml file from each of the configured groups, then
build the map of prefixes to plugin group/artifactIDs. If there is a
clash, initially it should fail. We might allow using the first
discovered or some other resolution mechanism, but would hope not to get
that situation as a goal representation might start taking on different
meanings in different contexts.
was:
We have a default rule which will be used as a fallback, where the
prefix "idea" is turned into "maven-idea-plugin". This will be retained
if no other information is found.
Before applying the default rule, some more metadata from the repository
will be consulted. This will be stored at the group level, and named
"plugins.xml".
/org/apache/maven/plugins/plugins.xml
/org.apache.maven.plugins/plugins.xml
While this could potentially include version information as well, it is
worth being able to check these on a plugin-by-plugin basis, and it also
fits with the potential RELEASE specifier on dependencies. This could be
reconsidered in future versions.
Format of the file for now is simple:
<prefixes>
<groupId>org.apache.maven.plugins</groupId>
<plugins>
<plugin>
<prefix>idea</prefix>
<artifactId>maven-idea-plugin</artifactId>
</plugin>
...
</plugins>
</prefixes>
This particular file will also be updated at release time for a plugin
(though it should rarely be necessary as only new additions need to be
published back).
The list of group IDs to search will be configured from settings.xml,
with the default being just org.apache.maven.plugins. The process will
be to load the plugins.xml file from each of the configured groups, then
build the map of prefixes to plugin group/artifactIDs. If there is a
clash, initially it should fail. We might allow using the first
discovered or some other resolution mechanism, but would hope not to get
that situation as a goal representation might start taking on different
meanings in different contexts.
Fix Version: (was: 2.0-alpha-3)
2.0-beta-1
Environment:
moving this one to beta-1, where we'll have time to get it right.
> implement group/artifactID looked by plugin prefix
> --------------------------------------------------
>
> Key: MNG-377
> URL: http://jira.codehaus.org/browse/MNG-377
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
>
> We have a default rule which will be used as a fallback, where the
> prefix "idea" is turned into "maven-idea-plugin". This will be retained
> if no other information is found.
> Before applying the default rule, some more metadata from the repository
> will be consulted. This will be stored at the group level, and named
> "plugins.xml".
> /org/apache/maven/plugins/plugins.xml
> /org.apache.maven.plugins/plugins.xml
> While this could potentially include version information as well, it is
> worth being able to check these on a plugin-by-plugin basis, and it also
> fits with the potential RELEASE specifier on dependencies. This could be
> reconsidered in future versions.
> Format of the file for now is simple:
> <prefixes>
> <groupId>org.apache.maven.plugins</groupId>
> <plugins>
> <plugin>
> <prefix>idea</prefix>
> <artifactId>maven-idea-plugin</artifactId>
> </plugin>
> ...
> </plugins>
> </prefixes>
> This particular file will also be updated at release time for a plugin
> (though it should rarely be necessary as only new additions need to be
> published back).
> The list of group IDs to search will be configured from settings.xml,
> with the default being just org.apache.maven.plugins. The process will
> be to load the plugins.xml file from each of the configured groups, then
> build the map of prefixes to plugin group/artifactIDs. If there is a
> clash, initially it should fail. We might allow using the first
> discovered or some other resolution mechanism, but would hope not to get
> that situation as a goal representation might start taking on different
> meanings in different contexts.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
