You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Roland Asmann <Ro...@cfc.at> on 2006/05/29 15:54:52 UTC
What does do??? (was: Excluding a JAR from WAR-generation)
Part of the problem was solved, but one question remains:
What does <dependentWarExcludes> in the war-plugin do???
Roland
On Monday 29 May 2006 15:52, Roland Asmann wrote:
> Okay, so I figured it out! The provided-scope DOES work, but I had an
> <exclusion> defined somewhere else, which for some reason removed my
> declaration of commons-logging...
> I've noticed, because I was checking a little more thorough and found that
> the version I set to provided (and also tried to exclude) was 1.0.3 and the
> included version was 1.0.4!
>
> So, I removed the <exclusion> and now the provided-scope does what it is
> supposed to do. Tried it several times, to make sure no random-behaviour
> remained.
>
> Roland
>
> On Monday 29 May 2006 15:24, Roland Asmann wrote:
> > Unfortunately yes. Per default I run it 'mvn clean install'.
> >
> > On Monday 29 May 2006 15:20, Kees de Kooter wrote:
> > > Does it also happen after you do an mvn clean?
> > >
> > > On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> > > > Yes, I know how to do that. But like I said, it doesn't always work
> > > > the way it is supposed to! I have no clue as to why this wouldn't
> > > > work, might be some sort of bug in Maven...
> > > >
> > > > Roland
> > > >
> > > > On Monday 29 May 2006 15:14, Kees de Kooter wrote:
> > > > > Just to make sure you understood my answer, this is how we do it:
> > > > >
> > > > > <dependency>
> > > > > <groupId>commons-logging</groupId>
> > > > > <artifactId>commons-logging</artifactId>
> > > > > <version>1.0.4</version>
> > > > > <scope>provided</scope>
> > > > > </dependency>
> > > > >
> > > > > It works for us, using maven 2.0.4
> > > > >
> > > > > On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> > > > > > That only seems to work at random! For some strange reason 3 out
> > > > > > of 5 builds are correct when the scope is set, but those other 2
> > > > > > builds still have the JAR!
> > > > > > I have no problem with building a couple of times more, but for
> > > > > > automated testing this is disastrous!
> > > > > >
> > > > > > Roland
> > > > > >
> > > > > > On Monday 29 May 2006 15:09, Kees de Kooter wrote:
> > > > > > > Give it scope "provided".
> > > > > > >
> > > > > > > On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I am building a WAR, in which I would like to remove some
> > > > > > > > JAR's that come up transitively. I've tried to configure my
> > > > > > > > war-plugin like this:
> > > > > > > >
> > > > > > > > <plugin>
> > > > > > > > <artifactId>maven-war-plugin</artifactId>
> > > > > > > > <configuration>
> > > > > > > > <archive>
> > > > > > > > <compress>false</compress>
> > > > > > > > <manifest>
> > > > > > > >
> > > > > > > > <addClasspath>true</addClasspath> </manifest>
> > > > > > > > </archive>
> > > > > > > >
> > > > > > > > <dependentWarExcludes>commons-logging</dependentWarExcludes>
> > > > > > > > </configuration>
> > > > > > > > </plugin>
> > > > > > > >
> > > > > > > > But this doesn't seem to work. Could anybody tell me how to
> > > > > > > > exclude commons-logging from the WAR? And also, could someone
> > > > > > > > explain what this 'dependentWarExcludes' does??
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > Roland
> > >
> > > ---------------------------------------------------------------------
> > > 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 : What does do???
Posted by Roland Asmann <Ro...@cfc.at>.
OK, so it indeed only happens when one of the dependencies is a WAR.
Thanks guys for the help!
Roland
On Monday 29 May 2006 16:40, Olivier Lamy wrote:
> Look http://jira.codehaus.org/browse/MWAR-33
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE : What does do???
Posted by Olivier Lamy <ol...@accor.com>.
Look http://jira.codehaus.org/browse/MWAR-33
--
Olivier
-----Message d'origine-----
De : Roland Asmann [mailto:Roland.Asmann@cfc.at]
Envoyé : lundi 29 mai 2006 16:35
À : Maven Users List
Objet : Re: What does <dependentWarExcludes> do???
So if I understand you correctly, it is for WAR(s) that have
dependencies on other WAR(s)? Then I indeed don't need this...
Roland
On Tuesday 30 May 2006 00:27, Pete Marvin King wrote:
> it's use for war overlays, for excluding dependent war files from
being
> included in the exploded war. this is use in war:exploded and
> war:inplace
>
> btw, only the artifacts with a runtime scope is included in the
war.
> when using war:war
>
>
> pete marvin
>
> Roland Asmann wrote:
> > Part of the problem was solved, but one question remains:
> >
> > What does <dependentWarExcludes> in the war-plugin do???
> >
> > Roland
> >
> > On Monday 29 May 2006 15:52, Roland Asmann wrote:
> >> Okay, so I figured it out! The provided-scope DOES work, but I had
> >> an <exclusion> defined somewhere else, which for some reason
> >> removed my declaration of commons-logging... I've noticed, because
> >> I was checking a little more thorough and found that the version I
> >> set to provided (and also tried to exclude) was 1.0.3 and the
> >> included version was 1.0.4!
> >>
> >> So, I removed the <exclusion> and now the provided-scope does what
> >> it is supposed to do. Tried it several times, to make sure no
> >> random-behaviour remained.
> >>
> >> Roland
> >>
> >> On Monday 29 May 2006 15:24, Roland Asmann wrote:
> >>> Unfortunately yes. Per default I run it 'mvn clean install'.
> >>>
> >>> On Monday 29 May 2006 15:20, Kees de Kooter wrote:
> >>>> Does it also happen after you do an mvn clean?
> >>>>
> >>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> >>>>> Yes, I know how to do that. But like I said, it doesn't always
> >>>>> work the way it is supposed to! I have no clue as to why this
> >>>>> wouldn't work, might be some sort of bug in Maven...
> >>>>>
> >>>>> Roland
> >>>>>
> >>>>> On Monday 29 May 2006 15:14, Kees de Kooter wrote:
> >>>>>> Just to make sure you understood my answer, this is how we do
> >>>>>> it:
> >>>>>>
> >>>>>> <dependency>
> >>>>>> <groupId>commons-logging</groupId>
> >>>>>> <artifactId>commons-logging</artifactId>
> >>>>>> <version>1.0.4</version>
> >>>>>> <scope>provided</scope>
> >>>>>> </dependency>
> >>>>>>
> >>>>>> It works for us, using maven 2.0.4
> >>>>>>
> >>>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> >>>>>>> That only seems to work at random! For some strange reason 3
> >>>>>>> out of 5 builds are correct when the scope is set, but those
> >>>>>>> other 2 builds still have the JAR! I have no problem with
> >>>>>>> building a couple of times more, but for automated testing
> >>>>>>> this is disastrous!
> >>>>>>>
> >>>>>>> Roland
> >>>>>>>
> >>>>>>> On Monday 29 May 2006 15:09, Kees de Kooter wrote:
> >>>>>>>> Give it scope "provided".
> >>>>>>>>
> >>>>>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> I am building a WAR, in which I would like to remove some
> >>>>>>>>> JAR's that come up transitively. I've tried to configure my
> >>>>>>>>> war-plugin like this:
> >>>>>>>>>
> >>>>>>>>> <plugin>
> >>>>>>>>> <artifactId>maven-war-plugin</artifactId>
> >>>>>>>>> <configuration>
> >>>>>>>>> <archive>
> >>>>>>>>> <compress>false</compress>
> >>>>>>>>> <manifest>
> >>>>>>>>>
> >>>>>>>>> <addClasspath>true</addClasspath> </manifest>
> >>>>>>>>> </archive>
> >>>>>>>>>
> >>>>>>>>> <dependentWarExcludes>commons-logging</dependentWarExcludes>
> >>>>>>>>> </configuration>
> >>>>>>>>> </plugin>
> >>>>>>>>>
> >>>>>>>>> But this doesn't seem to work. Could anybody tell me how to
> >>>>>>>>> exclude commons-logging from the WAR? And also, could
> >>>>>>>>> someone explain what this 'dependentWarExcludes' does??
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>>
> >>>>>>>>> Roland
> >>>>
> >>>> -----------------------------------------------------------------
> >>>> ----
> >>>> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited.
--------------------------------------------------------------------------------------------------------------
Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites.
-------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: What does do???
Posted by Roland Asmann <Ro...@cfc.at>.
So if I understand you correctly, it is for WAR(s) that have dependencies on other WAR(s)?
Then I indeed don't need this...
Roland
On Tuesday 30 May 2006 00:27, Pete Marvin King wrote:
> it's use for war overlays, for excluding dependent war files from being
> included in the exploded war. this is use in war:exploded and
> war:inplace
>
> btw, only the artifacts with a runtime scope is included in the war.
> when using war:war
>
>
> pete marvin
>
> Roland Asmann wrote:
> > Part of the problem was solved, but one question remains:
> >
> > What does <dependentWarExcludes> in the war-plugin do???
> >
> > Roland
> >
> > On Monday 29 May 2006 15:52, Roland Asmann wrote:
> >> Okay, so I figured it out! The provided-scope DOES work, but I had an
> >> <exclusion> defined somewhere else, which for some reason removed my
> >> declaration of commons-logging...
> >> I've noticed, because I was checking a little more thorough and found
> >> that the version I set to provided (and also tried to exclude) was 1.0.3
> >> and the included version was 1.0.4!
> >>
> >> So, I removed the <exclusion> and now the provided-scope does what it is
> >> supposed to do. Tried it several times, to make sure no random-behaviour
> >> remained.
> >>
> >> Roland
> >>
> >> On Monday 29 May 2006 15:24, Roland Asmann wrote:
> >>> Unfortunately yes. Per default I run it 'mvn clean install'.
> >>>
> >>> On Monday 29 May 2006 15:20, Kees de Kooter wrote:
> >>>> Does it also happen after you do an mvn clean?
> >>>>
> >>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> >>>>> Yes, I know how to do that. But like I said, it doesn't always work
> >>>>> the way it is supposed to! I have no clue as to why this wouldn't
> >>>>> work, might be some sort of bug in Maven...
> >>>>>
> >>>>> Roland
> >>>>>
> >>>>> On Monday 29 May 2006 15:14, Kees de Kooter wrote:
> >>>>>> Just to make sure you understood my answer, this is how we do it:
> >>>>>>
> >>>>>> <dependency>
> >>>>>> <groupId>commons-logging</groupId>
> >>>>>> <artifactId>commons-logging</artifactId>
> >>>>>> <version>1.0.4</version>
> >>>>>> <scope>provided</scope>
> >>>>>> </dependency>
> >>>>>>
> >>>>>> It works for us, using maven 2.0.4
> >>>>>>
> >>>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> >>>>>>> That only seems to work at random! For some strange reason 3 out
> >>>>>>> of 5 builds are correct when the scope is set, but those other 2
> >>>>>>> builds still have the JAR!
> >>>>>>> I have no problem with building a couple of times more, but for
> >>>>>>> automated testing this is disastrous!
> >>>>>>>
> >>>>>>> Roland
> >>>>>>>
> >>>>>>> On Monday 29 May 2006 15:09, Kees de Kooter wrote:
> >>>>>>>> Give it scope "provided".
> >>>>>>>>
> >>>>>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> I am building a WAR, in which I would like to remove some
> >>>>>>>>> JAR's that come up transitively. I've tried to configure my
> >>>>>>>>> war-plugin like this:
> >>>>>>>>>
> >>>>>>>>> <plugin>
> >>>>>>>>> <artifactId>maven-war-plugin</artifactId>
> >>>>>>>>> <configuration>
> >>>>>>>>> <archive>
> >>>>>>>>> <compress>false</compress>
> >>>>>>>>> <manifest>
> >>>>>>>>>
> >>>>>>>>> <addClasspath>true</addClasspath> </manifest>
> >>>>>>>>> </archive>
> >>>>>>>>>
> >>>>>>>>> <dependentWarExcludes>commons-logging</dependentWarExcludes>
> >>>>>>>>> </configuration>
> >>>>>>>>> </plugin>
> >>>>>>>>>
> >>>>>>>>> But this doesn't seem to work. Could anybody tell me how to
> >>>>>>>>> exclude commons-logging from the WAR? And also, could someone
> >>>>>>>>> explain what this 'dependentWarExcludes' does??
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>>
> >>>>>>>>> Roland
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: What does do???
Posted by Pete Marvin King <la...@gmail.com>.
it's use for war overlays, for excluding dependent war files from being
included in the exploded war. this is use in war:exploded and
war:inplace
btw, only the artifacts with a runtime scope is included in the war.
when using war:war
pete marvin
Roland Asmann wrote:
> Part of the problem was solved, but one question remains:
>
> What does <dependentWarExcludes> in the war-plugin do???
>
> Roland
>
>
>
> On Monday 29 May 2006 15:52, Roland Asmann wrote:
>
>> Okay, so I figured it out! The provided-scope DOES work, but I had an
>> <exclusion> defined somewhere else, which for some reason removed my
>> declaration of commons-logging...
>> I've noticed, because I was checking a little more thorough and found that
>> the version I set to provided (and also tried to exclude) was 1.0.3 and the
>> included version was 1.0.4!
>>
>> So, I removed the <exclusion> and now the provided-scope does what it is
>> supposed to do. Tried it several times, to make sure no random-behaviour
>> remained.
>>
>> Roland
>>
>> On Monday 29 May 2006 15:24, Roland Asmann wrote:
>>
>>> Unfortunately yes. Per default I run it 'mvn clean install'.
>>>
>>> On Monday 29 May 2006 15:20, Kees de Kooter wrote:
>>>
>>>> Does it also happen after you do an mvn clean?
>>>>
>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
>>>>
>>>>> Yes, I know how to do that. But like I said, it doesn't always work
>>>>> the way it is supposed to! I have no clue as to why this wouldn't
>>>>> work, might be some sort of bug in Maven...
>>>>>
>>>>> Roland
>>>>>
>>>>> On Monday 29 May 2006 15:14, Kees de Kooter wrote:
>>>>>
>>>>>> Just to make sure you understood my answer, this is how we do it:
>>>>>>
>>>>>> <dependency>
>>>>>> <groupId>commons-logging</groupId>
>>>>>> <artifactId>commons-logging</artifactId>
>>>>>> <version>1.0.4</version>
>>>>>> <scope>provided</scope>
>>>>>> </dependency>
>>>>>>
>>>>>> It works for us, using maven 2.0.4
>>>>>>
>>>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
>>>>>>
>>>>>>> That only seems to work at random! For some strange reason 3 out
>>>>>>> of 5 builds are correct when the scope is set, but those other 2
>>>>>>> builds still have the JAR!
>>>>>>> I have no problem with building a couple of times more, but for
>>>>>>> automated testing this is disastrous!
>>>>>>>
>>>>>>> Roland
>>>>>>>
>>>>>>> On Monday 29 May 2006 15:09, Kees de Kooter wrote:
>>>>>>>
>>>>>>>> Give it scope "provided".
>>>>>>>>
>>>>>>>> On 5/29/06, Roland Asmann <Ro...@cfc.at> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I am building a WAR, in which I would like to remove some
>>>>>>>>> JAR's that come up transitively. I've tried to configure my
>>>>>>>>> war-plugin like this:
>>>>>>>>>
>>>>>>>>> <plugin>
>>>>>>>>> <artifactId>maven-war-plugin</artifactId>
>>>>>>>>> <configuration>
>>>>>>>>> <archive>
>>>>>>>>> <compress>false</compress>
>>>>>>>>> <manifest>
>>>>>>>>>
>>>>>>>>> <addClasspath>true</addClasspath> </manifest>
>>>>>>>>> </archive>
>>>>>>>>>
>>>>>>>>> <dependentWarExcludes>commons-logging</dependentWarExcludes>
>>>>>>>>> </configuration>
>>>>>>>>> </plugin>
>>>>>>>>>
>>>>>>>>> But this doesn't seem to work. Could anybody tell me how to
>>>>>>>>> exclude commons-logging from the WAR? And also, could someone
>>>>>>>>> explain what this 'dependentWarExcludes' does??
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Roland
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>
>
>