[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_79369 ] Jonas Olsson commented on MEAR-42: ----------------------------------
I'm sorry, but I've gotten the impression that groupId as part of the filename is a Maven generic construct? So how does that not fit well? I see no other way to distinguish files in the same directory (e.g. APP-INF\lib) from each other other than by name, so concrete ideas are hard to come by. However, if you can instruct me on how I can interact with the EAR plugin to dynamically (i.e. without explicit plugin configuration) rename included dependencies, I won't need this feature included. > 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
