You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by jlo_gestalt <jl...@gestalt-llc.com> on 2008/05/01 19:26:05 UTC
How to get around maven causing CI to fail
I am not sure this is a bug or intentional, but it's very annoying how the
clean phase requires all the dependencies to run. It's annoying because our
CI environment (like everyone else) usually executes mvn clean install.
And if I have a multi module project, when adding a new module, CI fails
because the clean is unable to resolve dependencies.
For example, lets say I have the following module structure where B depends
on A
parent
- module A
- module B (depends (A))
CI works fine for many days executing mvn clean install and then I go and
commit a new module C where module B depends on my new module C:
parent
- module A
- module B (depends (A, C))
- module C
Since my CI environment hasn't built module C yet it fails with not being
able to resolve dependencies. The current workaround includes remoting into
our CI server and manually running mvn install.
To my knowledge this has been the way it has worked since maven 1.x and has
got to be the most frustrating maven feature I know of (and for me there are
few).
Does anyone know of a way to get around this? My team is getting tired of
this issue. It would be great if the clean plugin wouldn't fail, or their
was a way to override it with a property or something. this issue also
exists if you increment your projects version from say 1.5-SNAPSHOT to
1.6-SNAPSHOT.
FYI, we also have this issue during the validate phase when adding new
modules. The first goal our CI envirnonment runs is to rebuild the database
(which we have running during the validate phase). And when we add a new
module or increment our version CI fails.
--
View this message in context: http://www.nabble.com/How-to-get-around-maven-causing-CI-to-fail-tp16993340s177p16993340.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 to get around maven causing CI to fail
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
I don't necessarily need something immediate. I would much rather prefer
getting this fixed in future versions of maven.
Brian E Fox wrote:
>
> Only if you can find an old version of clean that doesn't fork (I know
> one exists). We should fix clean to behave better but that doesn't help
> you now.
>
> -----Original Message-----
> From: jlo_gestalt [mailto:jlorenzen@gestalt-llc.com]
> Sent: Friday, May 02, 2008 10:12 AM
> To: users@maven.apache.org
> Subject: RE: How to get around maven causing CI to fail
>
>
> Yes,
> that is exactly what I am referring to. Any way we can change this or
> provide an override ability?
>
>
> Brian E Fox wrote:
>>
>> Clean forks and executes so it can find additional output folders or
>> something (which I find annoying most of the time)... therefore it is
>> also going to try and download some dependencies that may not be in
> the
>> repo (particularly after a version change)
>>
>> -----Original Message-----
>> From: Brett Porter [mailto:brett.porter@gmail.com]
>> Sent: Thursday, May 01, 2008 9:58 PM
>> To: Maven Users List
>> Subject: Re: How to get around maven causing CI to fail
>>
>> The clean plugin itself doesn't require this - it's probably one of
>> the other plugins you have bound. Maven must resolve these plugins to
>> discover where they fit into the lifecycle, but I'm not sure why it
>> would be trying to resolve other modules in the project.
>>
>> - Brett
>>
>> 2008/5/2 jlo_gestalt <jl...@gestalt-llc.com>:
>>>
>>> I am not sure this is a bug or intentional, but it's very annoying
>> how the
>>> clean phase requires all the dependencies to run. It's annoying
>> because our
>>> CI environment (like everyone else) usually executes mvn clean
>> install.
>>>
>>> And if I have a multi module project, when adding a new module, CI
>> fails
>>> because the clean is unable to resolve dependencies.
>>>
>>> For example, lets say I have the following module structure where B
>> depends
>>> on A
>>>
>>> parent
>>> - module A
>>> - module B (depends (A))
>>>
>>> CI works fine for many days executing mvn clean install and then I
> go
>> and
>>> commit a new module C where module B depends on my new module C:
>>>
>>> parent
>>> - module A
>>> - module B (depends (A, C))
>>> - module C
>>>
>>> Since my CI environment hasn't built module C yet it fails with not
>> being
>>> able to resolve dependencies. The current workaround includes
>> remoting into
>>> our CI server and manually running mvn install.
>>>
>>> To my knowledge this has been the way it has worked since maven 1.x
>> and has
>>> got to be the most frustrating maven feature I know of (and for me
>> there are
>>> few).
>>>
>>> Does anyone know of a way to get around this? My team is getting
>> tired of
>>> this issue. It would be great if the clean plugin wouldn't fail, or
>> their
>>> was a way to override it with a property or something. this issue
>> also
>>> exists if you increment your projects version from say 1.5-SNAPSHOT
>> to
>>> 1.6-SNAPSHOT.
>>>
>>> FYI, we also have this issue during the validate phase when adding
>> new
>>> modules. The first goal our CI envirnonment runs is to rebuild the
>> database
>>> (which we have running during the validate phase). And when we add a
>> new
>>> module or increment our version CI fails.
>>> --
>>> View this message in context:
>>
> http://www.nabble.com/How-to-get-around-maven-causing-CI-to-fail-tp16993
>> 340s177p16993340.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
>>>
>>>
>>
>>
>>
>> --
>> Brett Porter
>> Blog: http://blogs.exist.com/bporter/
>>
>> ---------------------------------------------------------------------
>> 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-to-get-around-maven-causing-CI-to-fail-tp16993
> 340s177p17020186.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-to-get-around-maven-causing-CI-to-fail-tp16993340s177p17025607.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 to get around maven causing CI to fail
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Only if you can find an old version of clean that doesn't fork (I know
one exists). We should fix clean to behave better but that doesn't help
you now.
-----Original Message-----
From: jlo_gestalt [mailto:jlorenzen@gestalt-llc.com]
Sent: Friday, May 02, 2008 10:12 AM
To: users@maven.apache.org
Subject: RE: How to get around maven causing CI to fail
Yes,
that is exactly what I am referring to. Any way we can change this or
provide an override ability?
Brian E Fox wrote:
>
> Clean forks and executes so it can find additional output folders or
> something (which I find annoying most of the time)... therefore it is
> also going to try and download some dependencies that may not be in
the
> repo (particularly after a version change)
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Thursday, May 01, 2008 9:58 PM
> To: Maven Users List
> Subject: Re: How to get around maven causing CI to fail
>
> The clean plugin itself doesn't require this - it's probably one of
> the other plugins you have bound. Maven must resolve these plugins to
> discover where they fit into the lifecycle, but I'm not sure why it
> would be trying to resolve other modules in the project.
>
> - Brett
>
> 2008/5/2 jlo_gestalt <jl...@gestalt-llc.com>:
>>
>> I am not sure this is a bug or intentional, but it's very annoying
> how the
>> clean phase requires all the dependencies to run. It's annoying
> because our
>> CI environment (like everyone else) usually executes mvn clean
> install.
>>
>> And if I have a multi module project, when adding a new module, CI
> fails
>> because the clean is unable to resolve dependencies.
>>
>> For example, lets say I have the following module structure where B
> depends
>> on A
>>
>> parent
>> - module A
>> - module B (depends (A))
>>
>> CI works fine for many days executing mvn clean install and then I
go
> and
>> commit a new module C where module B depends on my new module C:
>>
>> parent
>> - module A
>> - module B (depends (A, C))
>> - module C
>>
>> Since my CI environment hasn't built module C yet it fails with not
> being
>> able to resolve dependencies. The current workaround includes
> remoting into
>> our CI server and manually running mvn install.
>>
>> To my knowledge this has been the way it has worked since maven 1.x
> and has
>> got to be the most frustrating maven feature I know of (and for me
> there are
>> few).
>>
>> Does anyone know of a way to get around this? My team is getting
> tired of
>> this issue. It would be great if the clean plugin wouldn't fail, or
> their
>> was a way to override it with a property or something. this issue
> also
>> exists if you increment your projects version from say 1.5-SNAPSHOT
> to
>> 1.6-SNAPSHOT.
>>
>> FYI, we also have this issue during the validate phase when adding
> new
>> modules. The first goal our CI envirnonment runs is to rebuild the
> database
>> (which we have running during the validate phase). And when we add a
> new
>> module or increment our version CI fails.
>> --
>> View this message in context:
>
http://www.nabble.com/How-to-get-around-maven-causing-CI-to-fail-tp16993
> 340s177p16993340.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
>>
>>
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> ---------------------------------------------------------------------
> 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-to-get-around-maven-causing-CI-to-fail-tp16993
340s177p17020186.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
RE: How to get around maven causing CI to fail
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
Yes,
that is exactly what I am referring to. Any way we can change this or
provide an override ability?
Brian E Fox wrote:
>
> Clean forks and executes so it can find additional output folders or
> something (which I find annoying most of the time)... therefore it is
> also going to try and download some dependencies that may not be in the
> repo (particularly after a version change)
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Thursday, May 01, 2008 9:58 PM
> To: Maven Users List
> Subject: Re: How to get around maven causing CI to fail
>
> The clean plugin itself doesn't require this - it's probably one of
> the other plugins you have bound. Maven must resolve these plugins to
> discover where they fit into the lifecycle, but I'm not sure why it
> would be trying to resolve other modules in the project.
>
> - Brett
>
> 2008/5/2 jlo_gestalt <jl...@gestalt-llc.com>:
>>
>> I am not sure this is a bug or intentional, but it's very annoying
> how the
>> clean phase requires all the dependencies to run. It's annoying
> because our
>> CI environment (like everyone else) usually executes mvn clean
> install.
>>
>> And if I have a multi module project, when adding a new module, CI
> fails
>> because the clean is unable to resolve dependencies.
>>
>> For example, lets say I have the following module structure where B
> depends
>> on A
>>
>> parent
>> - module A
>> - module B (depends (A))
>>
>> CI works fine for many days executing mvn clean install and then I go
> and
>> commit a new module C where module B depends on my new module C:
>>
>> parent
>> - module A
>> - module B (depends (A, C))
>> - module C
>>
>> Since my CI environment hasn't built module C yet it fails with not
> being
>> able to resolve dependencies. The current workaround includes
> remoting into
>> our CI server and manually running mvn install.
>>
>> To my knowledge this has been the way it has worked since maven 1.x
> and has
>> got to be the most frustrating maven feature I know of (and for me
> there are
>> few).
>>
>> Does anyone know of a way to get around this? My team is getting
> tired of
>> this issue. It would be great if the clean plugin wouldn't fail, or
> their
>> was a way to override it with a property or something. this issue
> also
>> exists if you increment your projects version from say 1.5-SNAPSHOT
> to
>> 1.6-SNAPSHOT.
>>
>> FYI, we also have this issue during the validate phase when adding
> new
>> modules. The first goal our CI envirnonment runs is to rebuild the
> database
>> (which we have running during the validate phase). And when we add a
> new
>> module or increment our version CI fails.
>> --
>> View this message in context:
> http://www.nabble.com/How-to-get-around-maven-causing-CI-to-fail-tp16993
> 340s177p16993340.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
>>
>>
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> ---------------------------------------------------------------------
> 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-to-get-around-maven-causing-CI-to-fail-tp16993340s177p17020186.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 to get around maven causing CI to fail
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Clean forks and executes so it can find additional output folders or
something (which I find annoying most of the time)... therefore it is
also going to try and download some dependencies that may not be in the
repo (particularly after a version change)
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: Thursday, May 01, 2008 9:58 PM
To: Maven Users List
Subject: Re: How to get around maven causing CI to fail
The clean plugin itself doesn't require this - it's probably one of
the other plugins you have bound. Maven must resolve these plugins to
discover where they fit into the lifecycle, but I'm not sure why it
would be trying to resolve other modules in the project.
- Brett
2008/5/2 jlo_gestalt <jl...@gestalt-llc.com>:
>
> I am not sure this is a bug or intentional, but it's very annoying
how the
> clean phase requires all the dependencies to run. It's annoying
because our
> CI environment (like everyone else) usually executes mvn clean
install.
>
> And if I have a multi module project, when adding a new module, CI
fails
> because the clean is unable to resolve dependencies.
>
> For example, lets say I have the following module structure where B
depends
> on A
>
> parent
> - module A
> - module B (depends (A))
>
> CI works fine for many days executing mvn clean install and then I go
and
> commit a new module C where module B depends on my new module C:
>
> parent
> - module A
> - module B (depends (A, C))
> - module C
>
> Since my CI environment hasn't built module C yet it fails with not
being
> able to resolve dependencies. The current workaround includes
remoting into
> our CI server and manually running mvn install.
>
> To my knowledge this has been the way it has worked since maven 1.x
and has
> got to be the most frustrating maven feature I know of (and for me
there are
> few).
>
> Does anyone know of a way to get around this? My team is getting
tired of
> this issue. It would be great if the clean plugin wouldn't fail, or
their
> was a way to override it with a property or something. this issue
also
> exists if you increment your projects version from say 1.5-SNAPSHOT
to
> 1.6-SNAPSHOT.
>
> FYI, we also have this issue during the validate phase when adding
new
> modules. The first goal our CI envirnonment runs is to rebuild the
database
> (which we have running during the validate phase). And when we add a
new
> module or increment our version CI fails.
> --
> View this message in context:
http://www.nabble.com/How-to-get-around-maven-causing-CI-to-fail-tp16993
340s177p16993340.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
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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: How to get around maven causing CI to fail
Posted by Brett Porter <br...@gmail.com>.
The clean plugin itself doesn't require this - it's probably one of
the other plugins you have bound. Maven must resolve these plugins to
discover where they fit into the lifecycle, but I'm not sure why it
would be trying to resolve other modules in the project.
- Brett
2008/5/2 jlo_gestalt <jl...@gestalt-llc.com>:
>
> I am not sure this is a bug or intentional, but it's very annoying how the
> clean phase requires all the dependencies to run. It's annoying because our
> CI environment (like everyone else) usually executes mvn clean install.
>
> And if I have a multi module project, when adding a new module, CI fails
> because the clean is unable to resolve dependencies.
>
> For example, lets say I have the following module structure where B depends
> on A
>
> parent
> - module A
> - module B (depends (A))
>
> CI works fine for many days executing mvn clean install and then I go and
> commit a new module C where module B depends on my new module C:
>
> parent
> - module A
> - module B (depends (A, C))
> - module C
>
> Since my CI environment hasn't built module C yet it fails with not being
> able to resolve dependencies. The current workaround includes remoting into
> our CI server and manually running mvn install.
>
> To my knowledge this has been the way it has worked since maven 1.x and has
> got to be the most frustrating maven feature I know of (and for me there are
> few).
>
> Does anyone know of a way to get around this? My team is getting tired of
> this issue. It would be great if the clean plugin wouldn't fail, or their
> was a way to override it with a property or something. this issue also
> exists if you increment your projects version from say 1.5-SNAPSHOT to
> 1.6-SNAPSHOT.
>
> FYI, we also have this issue during the validate phase when adding new
> modules. The first goal our CI envirnonment runs is to rebuild the database
> (which we have running during the validate phase). And when we add a new
> module or increment our version CI fails.
> --
> View this message in context: http://www.nabble.com/How-to-get-around-maven-causing-CI-to-fail-tp16993340s177p16993340.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
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org