aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes Release only one module in multimodule maven project Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "Release only one module in multimodule maven project " Watch "Release only one module in multimodule maven project " New topic
Author

Release only one module in multimodule maven project

sourabh girdhar
Ranch Hand

Joined: Feb 10, 2010
Posts: 71

I have one Multimodule maven projects which has nearly 20 modules. there is one common module which changes rarely and other 19 are independent of each other. Issue is when I change one module and go for release with hudson, It releases all modules.

If I go to specify version number for each module, it is very tedious job to change all numbers.

It is like increase in version number unneccessarily and also wastage of time/memory. For e.g. if I change each out of 19 twice , the common version will go to 1.39 or 39.0 which I don't want to avoid confusion. we are using standard release plugin.

Is there any way to manage release such that we can release only one module instead of whole project.

Thanks

SCJP SCWCD AIX SOA
The significant problems we face cannot be solved by the same level of thinking that created them -- Albert Einstein

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16236
    
  21

I think your problem is with Hudson and I haven't looked at Hudson yet. It's possible that your dependencies aren't set properly, however, if changing a satellite module triggers a rebuild of the shared module, and hence all the other satellite modules.

For a straight Maven build, it isn't so bad. You can check out the module of interest from the source repository and build just that one module.


Customer surveys are for companies who didn't pay proper attention to begin with.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5842
    
    7

Issue is when I change one module and go for release with hudson, It releases all modules.

Hudson will do this if the changed module is a dependency of the other modules (as noted in the pom.xml files of the other modules). This is the behavior that you want because when you change the one module you need to run the unit tests on the other modules to prevent regression errors.


JBoss In Action
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Release only one module in multimodule maven project