If you use the 2.2-SNAPSHOT version of the assembly plugin, you can specify
the <outputFileNameMapping> in the dependencySet to be something like the
following descriptor has:
<assembly>
<id>bin</id>
<formats>
<format>dir</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<dependencySets>
<dependencySet>
<unpack>false</unpack>
<outputDirectory>lib</outputDirectory>
<outputFileNameMapping>${artifactId}-${baseVersion}.${extension}</outputFileNameMapping>
</dependencySet>
</dependencySets>
</assembly>
-john
On 1/12/07, Christian Goetze <[EMAIL PROTECTED]> wrote:
So I have my jar plugin include the classpath in the manifest. That
classpath specifies the version text as x.y-SNAPSHOT. The assembly
plugin, on the other hand, packs the resolved snapshot name
(x.y-date.sig-buildnr) of the jars into the assembly, causing the
application to fail.
Is there a way to tell the assembly plugin to not do that?
--
cg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
