In that case, you're stuck and the release plugin will do the job but don't
use properties to define versions.
I think a certain version of Maven allows to import a pom into another.
Regards
Jeff
On Sat, Sep 26, 2009 at 7:09 PM, Emmanuel24 wrote:
>
> As I said, I define the version in ProjectP
As I said, I define the version in ProjectParent and in this project, I
defined my modules as the figure shows it.
But my modules don't inherit from this project. That is the problem.
Emmanuel.
jeffma...@jeffmaury.com wrote:
>
> In that case, I don't understand where the versions of your proj
In that case, I don't understand where the versions of your projects are
defined because if the parents are enterprise pom, you are not allowed to
modify them !!!
Jeff
On Sat, Sep 26, 2009 at 4:06 PM, Emmanuel24 wrote:
>
> Hi Jeff,
>
> Thank you for your answer. The problem is that I can't chan
Hi Jeff,
Thank you for your answer. The problem is that I can't change parent poms
because it's enterprise poms. My poms inherit from them to respect
enterprise archictecture choices.
Emmanuel.
Jeff MAURY wrote:
>
> From my experience with Maven, I discourage using properties for
> defining
>From my experience with Maven, I discourage using properties for
defining pom version, Maven does handle it correctly on some cases,
even if the properties are defined on the parent pom
I recommand using version herited from the parent and updating the
parent version with the version plugin
Jeff
Hello,
I have a multimodules project (ProjectParent) with each module has a super
pom's parent .
See the figure:
http://www.nabble.com/file/p25614127/Screen03.jpg
(red : parent, blue : module)
My problem is very simple. I can't manage the version of my modules from my
multimodules projec
