[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_79310 ]
Stephane Nicoll commented on MEAR-42:
-------------------------------------
it won't be the default (backward compatibiliy) but I understand it might be
handy and resolve conflicts.
However, I don't have the feeling it will fit with the way we use groupIds. For
instance, a groupId com.foo.bar will result in an artifact named
{noformat}
com.foo.bar-myartifact-1.0.jar
{noformat}
sounds really weird for a filename.
> General setting of dependency filenames
> ---------------------------------------
>
> Key: MEAR-42
> URL: http://jira.codehaus.org/browse/MEAR-42
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: Jonas Olsson
> Assigned To: Stephane Nicoll
> Priority: Minor
>
> When adding dependencies to the EAR, the "brief" filename from the repository
> is used (i.e. <artifactId>-<version>.jar).
> I some cases this will result in a name collision, required to be manually
> resolved with bundleFilename, but wouldn't an option to use the "full"
> filename (i.e. <groupId>-<artifactId>-<version>.jar) be better, allowing
> automatic re-use of the already established namespace?
--
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
