Cascading Maven releases...

[Jeff Vincent]

In our current set of projects we have multiple (30+) JAR files that are used by our 6 or 7 top-level web applications.  

At the end of each sprint, we perform a Maven release for all modules worked on or affected by an upstream dependency in that sprint.  It is quite time consuming to release all the modules and would seem to lend itself to a plugin that can automatically parse through the SNAPSHOT dependencies, determine if there is a current job for that artifact, then release all dependent projects.

Is there such a plugin or has anyone experimented with adding that capability?  I couldn't find anything but am interested in pursuing a solution.

Thanks!

--

Jeff Vincent
[hidden email]
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

I ♥ DropBox !! 

[Baptiste MATHUS-2]

Hi,
Are you sure you wouldn't just use a wrapping Maven multimodule build?

You're saying that you upgrade quite everybody at the end of each sprint. So there seems to be quite a hard link between those projects in terms of lifecycle. Isn't it?

And having heavily related projects is a multimodule need smell to me.

Cheers

Le 27 sept. 2012 00:20, "Jeff" <[hidden email]> a écrit :

In our current set of projects we have multiple (30+) JAR files that are used by our 6 or 7 top-level web applications.  

At the end of each sprint, we perform a Maven release for all modules worked on or affected by an upstream dependency in that sprint.  It is quite time consuming to release all the modules and would seem to lend itself to a plugin that can automatically parse through the SNAPSHOT dependencies, determine if there is a current job for that artifact, then release all dependent projects.

Is there such a plugin or has anyone experimented with adding that capability?  I couldn't find anything but am interested in pursuing a solution.

Thanks!

--

Jeff Vincent
[hidden email]
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

I ♥ DropBox !! 

[Jeff Vincent]

Not every project changes every iteration/sprint and the shared modules are shared by multiple top-level web applications so I don't think multi-module will work when they each are on different release schedules.  I also don't want to release modules that didn't change.  If it were multi-module then I'd have to release everything each sprint, right?

Thanks

On Sat, Sep 29, 2012 at 5:13 AM, Baptiste Mathus <[hidden email]> wrote:

Hi,
Are you sure you wouldn't just use a wrapping Maven multimodule build?

You're saying that you upgrade quite everybody at the end of each sprint. So there seems to be quite a hard link between those projects in terms of lifecycle. Isn't it?

And having heavily related projects is a multimodule need smell to me.

Cheers

Le 27 sept. 2012 00:20, "Jeff" <[hidden email]> a écrit :

In our current set of projects we have multiple (30+) JAR files that are used by our 6 or 7 top-level web applications.  

At the end of each sprint, we perform a Maven release for all modules worked on or affected by an upstream dependency in that sprint.  It is quite time consuming to release all the modules and would seem to lend itself to a plugin that can automatically parse through the SNAPSHOT dependencies, determine if there is a current job for that artifact, then release all dependent projects.

Is there such a plugin or has anyone experimented with adding that capability?  I couldn't find anything but am interested in pursuing a solution.

Thanks!

--

Jeff Vincent
[hidden email]
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

I ♥ DropBox !! 

--

Jeff Vincent
[hidden email]
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

I ♥ DropBox !!