We have a legacy project which is maven based. Everyone hates maven, and we
use ivy for other projects, thus, a migration is necessary.
I’d like to keep the existing file structure as is, and simply replace the
build scripts. That part is done. I need some help with how to
handle the versioning though.
Assume we have a multi module structure:
Root
/a
/b
/c
What I “think” should happen is that in the root directory I define a
version.properties file with the version. That version should propogate into
each submodule.
The ivy.xml in submodule b will list a dependency like this:
<dependency org="a" name="a" rev="${VERSION}"
conf="compile->runtime"/>
This works great as long you check out the root folder and always execute each
build from the top level aggregator. However, as we develop in eclipse,
people must check out each projects as standalone. Their isn’t a version
defined when running in that context.
Has anyone else faced this? How do you handle it? In maven, it works due to
the sub builds going to the repository and getting the parent pom…..
R
