commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dion Gillard <dion.gill...@gmail.com>
Subject Re: cvs commit: jakarta-commons/jelly project.xml
Date Mon, 22 Nov 2004 05:38:33 GMT
On Mon, 22 Nov 2004 13:00:47 +0800, Brett Porter <brett@apache.org> wrote:
> Is there any reason not to modify the inheritence to remove the entity?

Just the history of inheritance not quite working.

> 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've never understood removing the ability to use a standard XML
feature. I understand why it would be discouraged, but removing seems
wrong.


> 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?

Sounds good.

I've reverted to using 1.0.1 anyway as 1.1-SNAPSHOT of maven has issues ATM.
-- 
http://www.multitask.com.au/people/dion/

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message