Hi everybody,
we've been in a similar situation (and still are as we worked around it
copying the profile... ;-)
We would prefer "inheriting" another profile as a base for a new one -
from the same pom or a parent pom. This would perfectly match the
inheritance mechanism between whole poms...
Something like this:
<profile>
<id>first</id>
<properties>
<aProperty>aValue</aProperty>
<anotherProperty>anotherValue</anotherProperty>
</properties>
<build>
<plugins>
<plugin>
<artifactId>some.plugin</artifactId>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>extension_of_first</id>
<parent>first</parent> <!-- this inherits everything from the other
profile -->
<properties>
<aProperty>changedValue</aProperty> <!-- overwrite the value of
the property -->
<!-- anotherProperty is simply inherited and available here -->
</properties>
<!-- build is inherited and available here -->
</profile>
What do you think?
Or is this even possible and I have not yet discovered such a feature?
Thanks!
Andy
FarhanS wrote:
Hi Guys,
Though I have been told by Wayne that this isn't currently possible, so was
wondering which in the future 2.1.X or 3.X release might this be available
or if it is being planned for, at all ?
So basically I came to the need of making a profile which is an exactly
replica of an existing one except for one property. Instead of copy/pasting
all the values into this new profile, it would have been very useful if
there was a way to refer to a profile's property like
${profileA.propertyName}, but i guess we are not living in a perfect world
;)
Please comment..
Farhan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
