Brett,
We thought about adding the version numbers to a master pom but this
would cause trouble if we start branching.
I guess we will have to move away from our "project type" specific poms
to a single master pom and then we can use the moude-build pom to
define the versions.
Thanks
Stefan
Brett Porter wrote:
No, there is only single inheritance, so you can't have different
inheritance and a central location, unless there is a common ancestor
somewhere.
The setup you describe sounds rather confusing - Maven inheritance
differs from the object oriented concept in that it is largely
structural rather than "typed". Can you have the types share a single
ancestor so the module build and the inheritance hierarchy line up?
Cheers,
Brett
On 25/11/2008, at 8:10 AM, Stefan Fritz wrote:
Hi all,
We have multiple projects which should be built using a module build.
Each project is of a different type and therefore has a different parent
pom (not the module build pom!).
Now my problem is that I want to maintain the version at a central
place. The only solution I could think of is to have one master pom
where I define the module versions as properties in this pom.
As we will have many module builds this although will lead to a chaos
when branching multiple module builds.
Is there a way to have:
- projects built via a module build
- a central place for maintaining the modules version
- different parents per project in my module build
?
Thanks
Stefan
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
