In your dependencySet, specify the following: <useProjectArtifact>false</useProjectArtifact>
That should take care of things. On 9/2/10 3:21 AM, Barrie Treloar wrote:
I can't tell exactly when this occurred since we forked an internal release of 2.2 at r487459 where we have applied patches for * http://jira.codehaus.org/browse/MASSEMBLY-118 * http://jira.codehaus.org/browse/MASSEMBLY-166 * http://jira.codehaus.org/browse/MASSEMBLY-170 I suspect beta-1 has this new feature but I can't find it in the ChangeLog. Our descriptor uses <dependencySets> <dependencySet> <outputDirectory>lib</outputDirectory> <unpack>false</unpack> </dependencySet> </dependencySets> And previously the lib directory would have all the project's dependencies copied except for the project's main artifact. We would use <fileSets> <fileSet> <directory>target</directory> <outputDirectory></outputDirectory> <includes> <include>${artifactId}-${version}.jar</include> </includes> </fileSet> </fileSets> to copy this into the root of the archive. We are now finding that the main project artifact is also included in the dependencySet and thus appearing in lib/. Can anyone remember when this was changed so I can look up the reasoning and work out what we should be doing? I suspect we need to add an exclude... Suggestions most welcome. Barrie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
