This particular assembly descriptor is a one-time case for the assembly
plugin only. It's not the one that Brian was talking about, since that
one will have to be much more generalized to handle the variability of
other projects. In this case, I know that the build directory for the
assembly plugin is 'target' so there's no danger here. The descriptor
isn't included in the binary artifact, so we should be fine.
-john
Barrie Treloar wrote:
On Sat, Jun 13, 2009 at 7:40 AM, Barrie Treloar<[email protected]> wrote:
On Sat, Jun 13, 2009 at 7:21 AM, Barrie Treloar<[email protected]> wrote:
On Sat, Jun 13, 2009 at 12:04 AM, John Casey<[email protected]> wrote:
Is this still happening with maven-assembly-plugin 2.2-beta-4?
It was 2.2-beta-2, I'll check -4
2.2-beta-4 behaves correctly.
http://svn.apache.org/repos/asf/maven/plugins/branches/maven-assembly-plugin-2.2-beta-4/src/main/assembly/source-release.xml
uses ${project.build.directory} except in the excludes block:
<excludes>
<exclude>*.log</exclude>
<exclude>target/**</exclude>
</excludes>
I tried
<excludes>
<exclude>*.log</exclude>
<exclude>${project.build.directory}/**</exclude>
and it correctly gets replaced with target.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
