Perhaps it might be helpful in giving a solution, if we had the root
problem better described.
What are the particular properties of your application that makes it
unlike anything that has ever been built with Maven?
Maven is incredibly flexible and the technical expertise in this forum
is the best available.
However, just because you can make Maven do something (not the case this
time), does not mean that you should.
What are you trying to build and why is this project structure the best
way to do that?
Perhaps there is a simple way to get you a build structure that works well.
Ron
On 18/02/2011 2:21 AM, Anders Hammar wrote:
Neither does Maven 3.0. Possibly future version of Maven will have this
feature.
/Anders
On Fri, Feb 18, 2011 at 06:54, Anurag Kumar Nilesh<anur...@yahoo-inc.com>wrote:
Maven 2 doesn't have support for versionless parent pom.
You may use maven 3 instead
https://cwiki.apache.org/MAVEN/maven-3x.html
On 2/18/11 11:18 AM, "chandra.c49"<chandramohan....@gmail.com> wrote:
Hi ,
I've a maven project in the following structure setup --
Component1
--module1
--module2
--pom.xml
Component2 --> contains a<parent>
element referring to<Component1>
Component3 --> contains a<parent> element
referring to<Component1>
Component4 --> profiles.xml
and each team develops it's own component , hence they have a PROFILE
setup in their settings.xml file . This profile contians some properties
<path values ,versions etc..> used by the AD team locally .
few questions --
1) Can Component4 profiles.xml properties be used across other components
also. ?
2) The settings.xml file contains a profile with few properties set , and
this overrides all the other properties from all the components. But, it
does NOT for the<parent> element . how do we achieve this .?
for ex : Component2 contains a<parent> element referring to to
<Component1>
Component2 pom.xml file is below , with<relativePath>
element .
----------------------------------------
<parent>
<groupid>com.xyz.components</groupid>
<artifactId>component1</artifactid>
<relativePath>../${Comp1.Path}/pom.xml</relativePath>
</parent>
----------
As I try to execute from the Component2 , it first tries to scan the pom
file and fails as it can't find the Component1 pom file , due to not able
to
refer to the ${comp1.Path} property value from "settings.xml" file .
How can we achieve this, with out hardcoding the<relativePath> element
vlaue . Please let me know any other ways .
Thanks,
Chandra
--
View this message in context:
http://maven.40175.n5.nabble.com/how-can-we-replace-properties-values-in-the-parent-element-tp3390613p3390613.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
