You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by rd...@apache.org on 2004/01/11 21:59:09 UTC
cvs commit: jakarta-commons/betwixt project.xml
rdonkin 2004/01/11 12:59:09
Modified: betwixt project.xml
Log:
Added Tim as a developer. It'd probably be a good idea to have an xml file with entity definitions for commons developers so that the entry is the same in each project.xml.
Revision Changes Path
1.32 +6 -0 jakarta-commons/betwixt/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/betwixt/project.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- project.xml 11 Jan 2004 01:23:47 -0000 1.31
+++ project.xml 11 Jan 2004 20:59:09 -0000 1.32
@@ -94,6 +94,12 @@
<email>dlr@apache.org</email>
<organization>CollabNet</organization>
</developer>
+ <developer>
+ <name>Tim OBrien</name>
+ <id>tobrien</id>
+ <email>tobrien@apache.org</email>
+ <timezone>-6</timezone>
+ </developer>
</developers>
<dependencies>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-commons/betwixt project.xml
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On 11 Jan 2004, at 21:31, J.Pietschmann wrote:
> rdonkin@apache.org wrote:
>> Added Tim as a developer. It'd probably be a good idea to have an xml
>> file
>> with entity definitions for commons developers so that the entry is
>> the same
>> in each project.xml.
>
> Shared entities are a PITA for people who care only about certain
> subprojects
> (referencing shared files outside the subproject's directory generally
> sucks,
> especially if they don't make it into source distributions).
i agree in general terms but the mavenized component builds mostly
depend on the top level project.xml so i don't think that this would
really make things much worse than they are already. probably should
think about whether our source distributions need tweaking, though,
since it's unlikely they'll build out-of-the-box at the moment.
> I'd suggest do talk to the Maven people whether they could provide a
> sort
> of include mechanism with graceful fallback, somewhat like XInclude. Or
> actually use XInclude (pull out Cocoon's XInclude processor).
i had considered XInclude but concluded that it would probably impose a
greater overhead on developers. if we're moving towards unified
documentation builds, maybe this is something that could be addressed
when we have a single documentation build.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-commons/betwixt project.xml
Posted by "J.Pietschmann" <j3...@yahoo.de>.
rdonkin@apache.org wrote:
> Added Tim as a developer. It'd probably be a good idea to have an xml file
> with entity definitions for commons developers so that the entry is the same
> in each project.xml.
Shared entities are a PITA for people who care only about certain subprojects
(referencing shared files outside the subproject's directory generally sucks,
especially if they don't make it into source distributions).
I'd suggest do talk to the Maven people whether they could provide a sort
of include mechanism with graceful fallback, somewhat like XInclude. Or
actually use XInclude (pull out Cocoon's XInclude processor).
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org