Yep!
which was why I had only relativePath which would force you to check out
the parent.
i.e. it would be a child that _cannot_ be build without the parent, for use
by developers
the release plugin would (on the version tagged for release) replace the
relativePath tag with the released
I also think as Stephen,
Having an option to specify parent with relative path will be very helpfull,
I'm sure a solution can be found to provide this functionality.
Maybe something like having both relativePath and version and give
precedence to relativePath such that if it is found, it will be
On Jan 30, 2008 8:59 AM, Erez Nahir [EMAIL PROTECTED] wrote:
I also think as Stephen,
Having an option to specify parent with relative path will be very helpfull,
I'm sure a solution can be found to provide this functionality.
Maybe something like having both relativePath and version and give
I assume that's the case if you are with SVN (not my case, unfortunately
:-).
I thing maven should be version control agnostic, so, if the parent is
found in the relative path, use it, if not (either if the parent is not
checked out or if it is not in the path from any other reason) search the
Is there a way to use the version of a parent project in its childrens projects?
Arthur Rodrigues Stilben
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I am actually trying to use a property:
org.delta.esp.dap.version1.0.2/org.delta.esp.dap.version
Then use that property in my child pom's:
${org.delta.esp.dap.version}
When I do an install and deploy it seems to work, but when I am doing a
site-deploy, the parameter is not found and I get
That did not work on the parent:
parent
groupIdorg.delta.esp.dap.eep/groupId
artifactIdcommon/artifactId
*version${project.version}/version*
relativePath../pom.xml/relativePath
/parent
Still gives errors saying:
*Reason: Unable to download the artifact
I can comment out the modules version just fine then, but the parent:
parent
groupIdorg.delta.esp.dap.eep/groupId
artifactIdservices/artifactId
version1.0.2/version
relativePath../pom.xml/relativePath
/parent
Still is complaining if I do not have the
IMHO it should even be easier, just remove the version tag from the child
poms.
It will inherit the version from the parent.
Erez.
On Jan 29, 2008 9:52 PM, Manos Batsis [EMAIL PROTECTED] wrote:
I never actually managed to do that. IMHO that should be as easy as
I never actually managed to do that. IMHO that should be as easy as
version${project.parent.version}/version
Oh well :-)
Cheers,
Manos
Mick Knutson wrote:
I am actually trying to use a property:
org.delta.esp.dap.version1.0.2/org.delta.esp.dap.version
Then use that property in my child
We're doing just that on the project I am working on; no version
specified in the child POMs, and it gets inherited from the parent POM.
So since the child modules get the version implicitly, it should work
just referring to ${project.version}? (haven't tried it myself)
-Rune
Erez Nahir
AFAIR
property expansion is not performed in the parent tag... or maybe it's just
the version tag of the parent tag...
The logic is that it's not reproducible.
In my view this is the weakest link in Maven 2 as you then need to use the
release plugin to update all the child projects... makes
Hi Mick,
I don't think there is any way to do what you are trying to do.
Having modules in a directory tree is just an optimisation; maven should be
able to build any module when it is just checked out on its own.
In other words, the relativePath tag is just an optimisation that works
*when*
13 matches
Mail list logo
