You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ashley Williams <ag...@mac.com> on 2005/09/30 12:37:00 UTC
[m2] assembly plugin not preserving manifest settings
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] assembly plugin not preserving manifest settings
Posted by Brett Porter <br...@gmail.com>.
Unfortunately it is one of the few plugins still needing documentation.
http://maven.apache.org/maven2/plugins/maven-assembly-plugin/
We're still accepting volunteers :)
- Brett
On 9/30/05, Ashley Williams <ag...@mac.com> wrote:
> 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 <ag...@mac.com> 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: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] assembly plugin not preserving manifest settings
Posted by Ashley Williams <ag...@mac.com>.
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 <ag...@mac.com> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] assembly plugin not preserving manifest settings
Posted by Brett Porter <br...@gmail.com>.
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 <ag...@mac.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org