Ok fair enough - looks as though I will need to write my own assembly
file then.
Is there any documentation available for doing this?
On 30 Sep 2005, at 12:29, Brett Porter wrote:
Yes. You gave the manifest to the original JAR file, not the assembly.
The assembly is not aggregating the contents of the manifests.
- Brett
On 9/30/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
I currently have a project that I wish to build with manifest
classpath and dependency settings and so I added the following
plugin configs to my pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifest>
<mainClass>com.williams1000.delicious.Main</mainClass>
<addClasspath>true</addClasspath>
</manifest>
</archive>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptorId>jar-with-dependencies</
descriptorId>
</configuration>
</plugin>
however when I unpacked the jar file generated by m2
assembly:assembly, my manifest settings haven't been preserved. They
are present however in the install jar file. Is this the correct
behavior for the assemly plugin?
Thanks
AW
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
