You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Nitko2 <ni...@gmail.com> on 2005/12/14 16:45:21 UTC
Assembly plugin triggers execution of all previous phases
Hi!
I created my components.xml with assembly plugin associated with integration-test phase. I did so
because association with package phase caused infinite loop.
....
<integration-test>org.apache.maven.plugins:maven-assembly-plugin:2.0:assembly</integration-test>
....
This is pom.xml excerpt:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptor>assembly/descriptor.xml</descriptor>
<outputDirectory>target/work/output</outputDirectory>
<workDirectory>target/work</workDirectory>
</configuration>
</plugin>
When I start maven, integration-test phase causes all previous phases to run again.
Is this a bug? I suppose it is related to http://jira.codehaus.org/browse/MNG-1831
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Assembly plugin triggers execution of all previous phases
Posted by John Allen <jo...@hotmail.com>.
http://maven.apache.org/source-repository.html
-----Original Message-----
From: Nitko2 [mailto:nitko2@gmail.com]
Sent: 16 December 2005 07:55
To: Maven Users List
Subject: Re: Assembly plugin triggers execution of all previous phases
Ok, is there a way to turn it off. If not, can you point me to the code
where I can turn it off.
Then I'll copy it, name it decoupled-assembly and use it. This way I can use
assembly only in one
phase which is executed after package. And I need to use it in two phases.
Thanks, Filip.
John Allen wrote:
> As I stated before it is different because the developers believe assembly
> is not something that should be performed as part of a normal build
> lifecycle. The argument regarding what defines the scope of a lifecycle is
> moot.
>
> Re assembly being part of package phase:
>
>
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.ht
> ml
>
>
> ps. I had the same observations (and criticisms) when first encountering
> this behaviour.
>
> -----Original Message-----
> From: Nitko2 [mailto:nitko2@gmail.com]
> Sent: 15 December 2005 08:06
> To: Maven Users List
> Subject: Re: Assembly plugin triggers execution of all previous phases
>
> This doesn't make sense. If I remember correctly, assembly is a part od
> package phase in default
> lifecycle. And why is assembly plugin behaviour different from all other
> plugins(coupled with
> lifecycle phase)? In my opinion this breaks lifecycle main purpose.
>
>
>
>
> John Allen wrote:
>
>>assembly plugin is differenct to other lifecycle cooperating plugins in
>>as much as it invokes the package lifecyle before running. if you have
>>configured assembly to be part of package phase itself you will loop
>>forever.
>>
>>the idea is mvn assembly:assembly will do all the work of building an
>>assembly, including the dependent package build.
>>package = gets you jars et al. frequent
>>assembly = gets you null soft installers, zips and tgzs. infrequent.
>>
>>----- Original Message ----- From: "Nitko2" <ni...@gmail.com>
>>To: "Maven Users List" <us...@maven.apache.org>
>>Sent: Wednesday, December 14, 2005 3:45 PM
>>Subject: Assembly plugin triggers execution of all previous phases
>>
>>
>>
>>>Hi!
>>>
>>>I created my components.xml with assembly plugin associated with
>>>integration-test phase. I did so because association with package
>>>phase caused infinite loop.
>>>
>>>....
>>>
>
>
<integration-test>org.apache.maven.plugins:maven-assembly-plugin:2.0:assembl
> y</integration-test>
>
>>>....
>>>
>>>This is pom.xml excerpt:
>>>
>>><plugin>
>>> <artifactId>maven-assembly-plugin</artifactId>
>>> <configuration>
>>> <descriptor>assembly/descriptor.xml</descriptor>
>>> <outputDirectory>target/work/output</outputDirectory>
>>> <workDirectory>target/work</workDirectory>
>>> </configuration>
>>></plugin>
>>>
>>>
>>>When I start maven, integration-test phase causes all previous phases
>>>to run again.
>>>
>>>Is this a bug? I suppose it is related to
>>>http://jira.codehaus.org/browse/MNG-1831
>>>
>>>---------------------------------------------------------------------
>>>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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Assembly plugin triggers execution of all previous phases
Posted by Nitko2 <ni...@gmail.com>.
Ok, is there a way to turn it off. If not, can you point me to the code where I can turn it off.
Then I'll copy it, name it decoupled-assembly and use it. This way I can use assembly only in one
phase which is executed after package. And I need to use it in two phases.
Thanks, Filip.
John Allen wrote:
> As I stated before it is different because the developers believe assembly
> is not something that should be performed as part of a normal build
> lifecycle. The argument regarding what defines the scope of a lifecycle is
> moot.
>
> Re assembly being part of package phase:
>
> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.ht
> ml
>
>
> ps. I had the same observations (and criticisms) when first encountering
> this behaviour.
>
> -----Original Message-----
> From: Nitko2 [mailto:nitko2@gmail.com]
> Sent: 15 December 2005 08:06
> To: Maven Users List
> Subject: Re: Assembly plugin triggers execution of all previous phases
>
> This doesn't make sense. If I remember correctly, assembly is a part od
> package phase in default
> lifecycle. And why is assembly plugin behaviour different from all other
> plugins(coupled with
> lifecycle phase)? In my opinion this breaks lifecycle main purpose.
>
>
>
>
> John Allen wrote:
>
>>assembly plugin is differenct to other lifecycle cooperating plugins in
>>as much as it invokes the package lifecyle before running. if you have
>>configured assembly to be part of package phase itself you will loop
>>forever.
>>
>>the idea is mvn assembly:assembly will do all the work of building an
>>assembly, including the dependent package build.
>>package = gets you jars et al. frequent
>>assembly = gets you null soft installers, zips and tgzs. infrequent.
>>
>>----- Original Message ----- From: "Nitko2" <ni...@gmail.com>
>>To: "Maven Users List" <us...@maven.apache.org>
>>Sent: Wednesday, December 14, 2005 3:45 PM
>>Subject: Assembly plugin triggers execution of all previous phases
>>
>>
>>
>>>Hi!
>>>
>>>I created my components.xml with assembly plugin associated with
>>>integration-test phase. I did so because association with package
>>>phase caused infinite loop.
>>>
>>>....
>>>
>
> <integration-test>org.apache.maven.plugins:maven-assembly-plugin:2.0:assembl
> y</integration-test>
>
>>>....
>>>
>>>This is pom.xml excerpt:
>>>
>>><plugin>
>>> <artifactId>maven-assembly-plugin</artifactId>
>>> <configuration>
>>> <descriptor>assembly/descriptor.xml</descriptor>
>>> <outputDirectory>target/work/output</outputDirectory>
>>> <workDirectory>target/work</workDirectory>
>>> </configuration>
>>></plugin>
>>>
>>>
>>>When I start maven, integration-test phase causes all previous phases
>>>to run again.
>>>
>>>Is this a bug? I suppose it is related to
>>>http://jira.codehaus.org/browse/MNG-1831
>>>
>>>---------------------------------------------------------------------
>>>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: Assembly plugin triggers execution of all previous phases
Posted by John Allen <jo...@hotmail.com>.
As I stated before it is different because the developers believe assembly
is not something that should be performed as part of a normal build
lifecycle. The argument regarding what defines the scope of a lifecycle is
moot.
Re assembly being part of package phase:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.ht
ml
ps. I had the same observations (and criticisms) when first encountering
this behaviour.
-----Original Message-----
From: Nitko2 [mailto:nitko2@gmail.com]
Sent: 15 December 2005 08:06
To: Maven Users List
Subject: Re: Assembly plugin triggers execution of all previous phases
This doesn't make sense. If I remember correctly, assembly is a part od
package phase in default
lifecycle. And why is assembly plugin behaviour different from all other
plugins(coupled with
lifecycle phase)? In my opinion this breaks lifecycle main purpose.
John Allen wrote:
> assembly plugin is differenct to other lifecycle cooperating plugins in
> as much as it invokes the package lifecyle before running. if you have
> configured assembly to be part of package phase itself you will loop
> forever.
>
> the idea is mvn assembly:assembly will do all the work of building an
> assembly, including the dependent package build.
> package = gets you jars et al. frequent
> assembly = gets you null soft installers, zips and tgzs. infrequent.
>
> ----- Original Message ----- From: "Nitko2" <ni...@gmail.com>
> To: "Maven Users List" <us...@maven.apache.org>
> Sent: Wednesday, December 14, 2005 3:45 PM
> Subject: Assembly plugin triggers execution of all previous phases
>
>
>> Hi!
>>
>> I created my components.xml with assembly plugin associated with
>> integration-test phase. I did so because association with package
>> phase caused infinite loop.
>>
>> ....
>>
<integration-test>org.apache.maven.plugins:maven-assembly-plugin:2.0:assembl
y</integration-test>
>>
>> ....
>>
>> This is pom.xml excerpt:
>>
>> <plugin>
>> <artifactId>maven-assembly-plugin</artifactId>
>> <configuration>
>> <descriptor>assembly/descriptor.xml</descriptor>
>> <outputDirectory>target/work/output</outputDirectory>
>> <workDirectory>target/work</workDirectory>
>> </configuration>
>> </plugin>
>>
>>
>> When I start maven, integration-test phase causes all previous phases
>> to run again.
>>
>> Is this a bug? I suppose it is related to
>> http://jira.codehaus.org/browse/MNG-1831
>>
>> ---------------------------------------------------------------------
>> 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: Assembly plugin triggers execution of all previous phases
Posted by Nitko2 <ni...@gmail.com>.
This doesn't make sense. If I remember correctly, assembly is a part od package phase in default
lifecycle. And why is assembly plugin behaviour different from all other plugins(coupled with
lifecycle phase)? In my opinion this breaks lifecycle main purpose.
John Allen wrote:
> assembly plugin is differenct to other lifecycle cooperating plugins in
> as much as it invokes the package lifecyle before running. if you have
> configured assembly to be part of package phase itself you will loop
> forever.
>
> the idea is mvn assembly:assembly will do all the work of building an
> assembly, including the dependent package build.
> package = gets you jars et al. frequent
> assembly = gets you null soft installers, zips and tgzs. infrequent.
>
> ----- Original Message ----- From: "Nitko2" <ni...@gmail.com>
> To: "Maven Users List" <us...@maven.apache.org>
> Sent: Wednesday, December 14, 2005 3:45 PM
> Subject: Assembly plugin triggers execution of all previous phases
>
>
>> Hi!
>>
>> I created my components.xml with assembly plugin associated with
>> integration-test phase. I did so because association with package
>> phase caused infinite loop.
>>
>> ....
>> <integration-test>org.apache.maven.plugins:maven-assembly-plugin:2.0:assembly</integration-test>
>>
>> ....
>>
>> This is pom.xml excerpt:
>>
>> <plugin>
>> <artifactId>maven-assembly-plugin</artifactId>
>> <configuration>
>> <descriptor>assembly/descriptor.xml</descriptor>
>> <outputDirectory>target/work/output</outputDirectory>
>> <workDirectory>target/work</workDirectory>
>> </configuration>
>> </plugin>
>>
>>
>> When I start maven, integration-test phase causes all previous phases
>> to run again.
>>
>> Is this a bug? I suppose it is related to
>> http://jira.codehaus.org/browse/MNG-1831
>>
>> ---------------------------------------------------------------------
>> 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: Assembly plugin triggers execution of all previous phases
Posted by John Allen <jo...@hotmail.com>.
assembly plugin is differenct to other lifecycle cooperating plugins in as
much as it invokes the package lifecyle before running. if you have
configured assembly to be part of package phase itself you will loop
forever.
the idea is mvn assembly:assembly will do all the work of building an
assembly, including the dependent package build.
package = gets you jars et al. frequent
assembly = gets you null soft installers, zips and tgzs. infrequent.
----- Original Message -----
From: "Nitko2" <ni...@gmail.com>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Wednesday, December 14, 2005 3:45 PM
Subject: Assembly plugin triggers execution of all previous phases
> Hi!
>
> I created my components.xml with assembly plugin associated with
> integration-test phase. I did so because association with package phase
> caused infinite loop.
>
> ....
> <integration-test>org.apache.maven.plugins:maven-assembly-plugin:2.0:assembly</integration-test>
> ....
>
> This is pom.xml excerpt:
>
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>assembly/descriptor.xml</descriptor>
> <outputDirectory>target/work/output</outputDirectory>
> <workDirectory>target/work</workDirectory>
> </configuration>
> </plugin>
>
>
> When I start maven, integration-test phase causes all previous phases to
> run again.
>
> Is this a bug? I suppose it is related to
> http://jira.codehaus.org/browse/MNG-1831
>
> ---------------------------------------------------------------------
> 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