The way we handle this in the Geomajas project is for (sets of) modules
to have their own version and have one module (the -dep module) which
only contains a pom with dependencyManagement section which defines the
latest version of all modules (actually this pulls in the parent module
for each set of modules to assure all dependency versions contained in
the dependencyManagement of these modules are pulled in).
Hoping my explanation is somewhat understandable.
Kind regards,
Joachim
On 03/09/2011 12:47 AM, Daryl Lonnon wrote:
Hi, hopefully someone can help me with this.
So I have a situation where I have a project with multiple sub-projects.
Some of the sub-projects depend on one another.
I'd like to version the sub-projects independently while still releasing
something that defines the project as a whole. Some of the sub-projects have
associated resources files that can be quite large, so ideally you wouldn't
have to re-release them if they haven't changed. Also it'd be nice if after
a release, the development environment reverts back to the next versions
SNAPSHOTs.
So my wish list looks like:
1. I'd like to version the sub projects independently.
2. I'd like to be able to release a "global" version which defines the set
of sub-projects that work with one another.
3. I'd like to not release sub-projects that haven't changed just to release
a "global" version.
4. I'd like to have my development environment be cohesive after a release
(i.e. point to my local repositiories SNAPSHOTS for the sub-project
inter-dependencies)..
Has anyone ever tried to do something like this?
I've found:
http://out-println.blogspot.com/2008/10/maven-modules-with-independent-versions.html
but that scheme doesn't support wish 4 as far as I can tell.
Daryl
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
