[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_79363 ] Jonas Olsson commented on MEAR-42: ----------------------------------
It's not the "weirdness" of the filename that's relevant, it's the name collisions. As Maven has introduced groupId to negate artifact collisions it seems very natural to use the very same mechanism for filename collisions. Either you introduce a "finalName" attribute applicable generically to all included jars or you honor the "finalName" attribute of each inclusion. That's if this feature's going in. > 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
