You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by youhaodeyi <yo...@gmail.com> on 2008/11/24 05:34:00 UTC

A problem about MANIFEST in maven

I use maven-jar-plugin to handle the manifest file, see below configuration:

<manifest>
	<addClasspath>true</addClasspath>
        ...

And I have a dependency with system scope:
<dependency>
			<groupId>protocol</groupId>
			<artifactId>protocol</artifactId>
			<version>1.0</version>
			<scope>system</scope>
			<systemPath>${basedir}/src/main/libs/protocol.jar</systemPath>
</dependency>

But when run the command "mvn package" and the manifest file in the jar
doesn't contain this dependency.
How can I fix this?

thanks.
-- 
View this message in context: http://www.nabble.com/A-problem-about-MANIFEST-in-maven-tp20654786p20654786.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: A problem about MANIFEST in maven

Posted by Kalle Korhonen <ka...@gmail.com>.
But it'd be far easier if you just deployed the protocol.jar in your
internal repository and not try to use it as a dependency checked in with
the sources.

Kalle


On Mon, Nov 24, 2008 at 12:37 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:

> You'll have to generate your own manifest and not have jar generate it for
> you
>
> 2008/11/24 youhaodeyi <yo...@gmail.com>
>
> >
> > But what I want to do is to use maven assembly to deliver a release
> version
> > then put it on other machines where may not have such dependency. How can
> I
> > add it to the manifest file?
> >
> >
> > Stephen Connolly-2 wrote:
> > >
> > > system scope implies that the dependency is already on the system
> > > classpath, so maven does not need to add it
> > >
> > > Sent from my iPod
> > >
> > > On 24 Nov 2008, at 04:34, youhaodeyi <yo...@gmail.com> wrote:
> > >
> > >>
> > >> I use maven-jar-plugin to handle the manifest file, see below
> > >> configuration:
> > >>
> > >> <manifest>
> > >>    <addClasspath>true</addClasspath>
> > >>        ...
> > >>
> > >> And I have a dependency with system scope:
> > >> <dependency>
> > >>            <groupId>protocol</groupId>
> > >>            <artifactId>protocol</artifactId>
> > >>            <version>1.0</version>
> > >>            <scope>system</scope>
> > >>            <systemPath>${basedir}/src/main/libs/protocol.jar</
> > >> systemPath>
> > >> </dependency>
> > >>
> > >> But when run the command "mvn package" and the manifest file in the
> > >> jar
> > >> doesn't contain this dependency.
> > >> How can I fix this?
> > >>
> > >> thanks.
> > >> --
> > >> View this message in context:
> > >>
> >
> http://www.nabble.com/A-problem-about-MANIFEST-in-maven-tp20654786p20654786.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/A-problem-about-MANIFEST-in-maven-tp20654786p20656135.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: A problem about MANIFEST in maven

Posted by Stephen Connolly <st...@gmail.com>.
You'll have to generate your own manifest and not have jar generate it for
you

2008/11/24 youhaodeyi <yo...@gmail.com>

>
> But what I want to do is to use maven assembly to deliver a release version
> then put it on other machines where may not have such dependency. How can I
> add it to the manifest file?
>
>
> Stephen Connolly-2 wrote:
> >
> > system scope implies that the dependency is already on the system
> > classpath, so maven does not need to add it
> >
> > Sent from my iPod
> >
> > On 24 Nov 2008, at 04:34, youhaodeyi <yo...@gmail.com> wrote:
> >
> >>
> >> I use maven-jar-plugin to handle the manifest file, see below
> >> configuration:
> >>
> >> <manifest>
> >>    <addClasspath>true</addClasspath>
> >>        ...
> >>
> >> And I have a dependency with system scope:
> >> <dependency>
> >>            <groupId>protocol</groupId>
> >>            <artifactId>protocol</artifactId>
> >>            <version>1.0</version>
> >>            <scope>system</scope>
> >>            <systemPath>${basedir}/src/main/libs/protocol.jar</
> >> systemPath>
> >> </dependency>
> >>
> >> But when run the command "mvn package" and the manifest file in the
> >> jar
> >> doesn't contain this dependency.
> >> How can I fix this?
> >>
> >> thanks.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/A-problem-about-MANIFEST-in-maven-tp20654786p20654786.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/A-problem-about-MANIFEST-in-maven-tp20654786p20656135.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: A problem about MANIFEST in maven

Posted by youhaodeyi <yo...@gmail.com>.
But what I want to do is to use maven assembly to deliver a release version
then put it on other machines where may not have such dependency. How can I
add it to the manifest file?


Stephen Connolly-2 wrote:
> 
> system scope implies that the dependency is already on the system  
> classpath, so maven does not need to add it
> 
> Sent from my iPod
> 
> On 24 Nov 2008, at 04:34, youhaodeyi <yo...@gmail.com> wrote:
> 
>>
>> I use maven-jar-plugin to handle the manifest file, see below  
>> configuration:
>>
>> <manifest>
>>    <addClasspath>true</addClasspath>
>>        ...
>>
>> And I have a dependency with system scope:
>> <dependency>
>>            <groupId>protocol</groupId>
>>            <artifactId>protocol</artifactId>
>>            <version>1.0</version>
>>            <scope>system</scope>
>>            <systemPath>${basedir}/src/main/libs/protocol.jar</ 
>> systemPath>
>> </dependency>
>>
>> But when run the command "mvn package" and the manifest file in the  
>> jar
>> doesn't contain this dependency.
>> How can I fix this?
>>
>> thanks.
>> -- 
>> View this message in context:
>> http://www.nabble.com/A-problem-about-MANIFEST-in-maven-tp20654786p20654786.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/A-problem-about-MANIFEST-in-maven-tp20654786p20656135.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: A problem about MANIFEST in maven

Posted by Stephen Connolly <st...@gmail.com>.
system scope implies that the dependency is already on the system  
classpath, so maven does not need to add it

Sent from my iPod

On 24 Nov 2008, at 04:34, youhaodeyi <yo...@gmail.com> wrote:

>
> I use maven-jar-plugin to handle the manifest file, see below  
> configuration:
>
> <manifest>
>    <addClasspath>true</addClasspath>
>        ...
>
> And I have a dependency with system scope:
> <dependency>
>            <groupId>protocol</groupId>
>            <artifactId>protocol</artifactId>
>            <version>1.0</version>
>            <scope>system</scope>
>            <systemPath>${basedir}/src/main/libs/protocol.jar</ 
> systemPath>
> </dependency>
>
> But when run the command "mvn package" and the manifest file in the  
> jar
> doesn't contain this dependency.
> How can I fix this?
>
> thanks.
> -- 
> View this message in context: http://www.nabble.com/A-problem-about-MANIFEST-in-maven-tp20654786p20654786.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