Is there any reason not to modify the inheritence to remove the entity?
http://maven.apache.org/faq.html#using-entities
(I need to update this entry to mention that inheritence can be used as a
solution).
I think something like this in terms of hierarchy:
commons-build/project.xml
|
+-> jelly/shared-dependencies.xml
|
+-> jelly/project.xml
+-> jelly-tags/project.xml
So shared-dependencies.xml would look like:
<!-- LICENSE GOES HERE -->
<project>
<extend>../commons-build/project.xml</extend>
<dependencies>
...
</dependencies>
</project>
And the other project.xml files would extend that instead of commons-build, and
omit the entity.
WDYT?
Cheers,
Brett
Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
> dion 2004/11/21 19:12:56
>
> Modified: jelly project.xml
> Log:
> Put back entity that scm:prepare-release removed
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
