You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by legolas <le...@gmail.com> on 2009/01/03 21:04:23 UTC
how I can ensure that Maven include my own MANIFEST.MF instead of
its generated one?
Hi
Thank you for reading my post
Can someone please let me know how I can ensure that Maven uses my own
Manifest.MF instead of the one it generates?
I tried to use <include>**/*.MF</include> to ensure that it will include my
file but it uses its own generated file which is not what I need. I test the
syntax of <include>**/*.MF</include> and it works for other files and not
for the Manifest.mf
Thanks.
--
View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: how I can ensure that Maven include my own MANIFEST.MF instead
of its generated one?
Posted by "sarah.kho" <sa...@gmail.com>.
Hi
Thank you for your reply.
I used the following code inside the build element to make it possible to
use my own manifest file but it is not including the file into the final
archite.
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
</plugins>
Is there anything else which I should do? is there any way to ensure that
maven execute tasks associated with these elements?
Thanks
Brett Randall-2 wrote:
>
> <plugins> are covered in the Maven POM reference here
> http://maven.apache.org/pom.html#Plugins . They are nested within a
> <build>.
>
> On Sun, Jan 4, 2009 at 11:00 AM, sarah.kho <sa...@gmail.com> wrote:
>
>>
>> Thank you for the link, unfortunately my build file has no <plugins> tag
>> inside it. An I can not find out where I should put those tags. dot hey
>> goes inside the </parent> tag?
>>
>> Thanks
>>
>>
>>
>>
>>
>> Olivier Lamy wrote:
>> >
>> > Hi,
>> > Maybe have a look here
>> >
>> http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
>> > .
>> >
>> > HTH,
>> > --
>> > Olivier
>> >
>> > 2009/1/3 legolas <le...@gmail.com>:
>> >>
>> >> Hi
>> >> Thank you for reading my post
>> >> Can someone please let me know how I can ensure that Maven uses my own
>> >> Manifest.MF instead of the one it generates?
>> >> I tried to use <include>**/*.MF</include> to ensure that it will
>> include
>> >> my
>> >> file but it uses its own generated file which is not what I need. I
>> test
>> >> the
>> >> syntax of <include>**/*.MF</include> and it works for other files and
>> not
>> >> for the Manifest.mf
>> >>
>> >> Thanks.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.html
>> >> Sent from the Maven - Users mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21309292.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
Posted by Brett Randall <ja...@gmail.com>.
<plugins> are covered in the Maven POM reference here
http://maven.apache.org/pom.html#Plugins . They are nested within a
<build>.
On Sun, Jan 4, 2009 at 11:00 AM, sarah.kho <sa...@gmail.com> wrote:
>
> Thank you for the link, unfortunately my build file has no <plugins> tag
> inside it. An I can not find out where I should put those tags. dot hey
> goes inside the </parent> tag?
>
> Thanks
>
>
>
>
>
> Olivier Lamy wrote:
> >
> > Hi,
> > Maybe have a look here
> > http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
> > .
> >
> > HTH,
> > --
> > Olivier
> >
> > 2009/1/3 legolas <le...@gmail.com>:
> >>
> >> Hi
> >> Thank you for reading my post
> >> Can someone please let me know how I can ensure that Maven uses my own
> >> Manifest.MF instead of the one it generates?
> >> I tried to use <include>**/*.MF</include> to ensure that it will include
> >> my
> >> file but it uses its own generated file which is not what I need. I test
> >> the
> >> syntax of <include>**/*.MF</include> and it works for other files and
> not
> >> for the Manifest.mf
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: how I can ensure that Maven include my own MANIFEST.MF instead
of its generated one?
Posted by "sarah.kho" <sa...@gmail.com>.
Thank you for the link, unfortunately my build file has no <plugins> tag
inside it. An I can not find out where I should put those tags. dot hey
goes inside the </parent> tag?
Thanks
Olivier Lamy wrote:
>
> Hi,
> Maybe have a look here
> http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
> .
>
> HTH,
> --
> Olivier
>
> 2009/1/3 legolas <le...@gmail.com>:
>>
>> Hi
>> Thank you for reading my post
>> Can someone please let me know how I can ensure that Maven uses my own
>> Manifest.MF instead of the one it generates?
>> I tried to use <include>**/*.MF</include> to ensure that it will include
>> my
>> file but it uses its own generated file which is not what I need. I test
>> the
>> syntax of <include>**/*.MF</include> and it works for other files and not
>> for the Manifest.mf
>>
>> Thanks.
>> --
>> View this message in context:
>> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
>
--
View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Maybe have a look here
http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
.
HTH,
--
Olivier
2009/1/3 legolas <le...@gmail.com>:
>
> Hi
> Thank you for reading my post
> Can someone please let me know how I can ensure that Maven uses my own
> Manifest.MF instead of the one it generates?
> I tried to use <include>**/*.MF</include> to ensure that it will include my
> file but it uses its own generated file which is not what I need. I test the
> syntax of <include>**/*.MF</include> and it works for other files and not
> for the Manifest.mf
>
> Thanks.
> --
> View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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