[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_79365 ] Stephane Nicoll commented on MEAR-42: -------------------------------------
I am not saying there is no problem, I am saying that using the groupId as part of the file *name* won't fit well. I'll think over a solution, knowing that reallocating artifacts within the archive might be hard (so the filename should handle the conflict). If you have concrete ideas, let me know. > 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
