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

Reply via email to