Personally, I was going to suggest going the other direction and completely get
rid of the "parent" pom and move everything into the top level pom. We
already have a non-standard maven layout due to the parent pom which can be
confusing for people (and tools). I'd much rather try and find a
Hi
Yeah Babak's idea sounds good. Having that 2-level of parents.
On Sun, Aug 18, 2013 at 1:55 PM, Babak Vahdat
wrote:
> I just tried out a different approach which:
>
> - doesn't require any Maven plugin usage.
> - doesn't require to convert the Maven properties from the XML format to the
> Jav
I just tried out a different approach which:
- doesn't require any Maven plugin usage.
- doesn't require to convert the Maven properties from the XML format to the
Java properties file format etc.
- is really simple.
So the idea is to simply bump one more level of parent-child dependency into
our
Hi,
Why don't you do it the other way around?
I understand from Claus that his desire is not so much to manage the
dependencies and their versions in a different file, but just to provide a
file where the version properties can be easily read from and diffed
between releases.
In that case, you c
Is there a plugin you are aware of which supports this? If yes, +1
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/member
