Re: maven-assembly-plugin 2.2-beta-X: dependencySet is now including project artifact in outputDirectory
On Fri, Sep 3, 2010 at 9:46 AM, Barrie Treloar wrote: > On Thu, Sep 2, 2010 at 11:48 PM, John Casey wrote: >> In your dependencySet, specify the following: >> >> false > > Cheers. > > Did I just miss this in the documentation (other than in the > configuration page)? > > I've had another look around the doco now that I know what to look for > and can't see it. > > I'd like to add it to > http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html > since it has an example of dependencySet and exclusion. > > Your thoughts? > I've added to that page - since it looks like I wrote it in the first place :) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin 2.2-beta-X: dependencySet is now including project artifact in outputDirectory
On Thu, Sep 2, 2010 at 11:48 PM, John Casey wrote: > In your dependencySet, specify the following: > > false Cheers. Did I just miss this in the documentation (other than in the configuration page)? I've had another look around the doco now that I know what to look for and can't see it. I'd like to add it to http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html since it has an example of dependencySet and exclusion. Your thoughts? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin 2.2-beta-X: dependencySet is now including project artifact in outputDirectory
BTW, this was added for http://jira.codehaus.org/browse/MASSEMBLY-197,
in revId 549995.
-j
On 9/2/10 10:18 AM, John Casey wrote:
In your dependencySet, specify the following:
false
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
lib
false
And previously the lib directory would have all the project's
dependencies copied except for the project's main artifact.
We would use
target
${artifactId}-${version}.jar
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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-assembly-plugin 2.2-beta-X: dependencySet is now including project artifact in outputDirectory
In your dependencySet, specify the following:
false
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
lib
false
And previously the lib directory would have all the project's
dependencies copied except for the project's main artifact.
We would use
target
${artifactId}-${version}.jar
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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
maven-assembly-plugin 2.2-beta-X: dependencySet is now including project artifact in outputDirectory
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
lib
false
And previously the lib directory would have all the project's
dependencies copied except for the project's main artifact.
We would use
target
${artifactId}-${version}.jar
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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
