The Alexandria project with Gump, Maveric, et. al.
are doing a great job of keeping all the builds working
with each other.  It also helps with notifying projects
of changes in the API.

But there hasn't been any official documentation or requests
for target naming conventions like I just proposed.  If everyone
likes the approach, Ant should place the information in their
manual (like gnumake does with its conventions)--and all project
leaders should either make the modifications to the build
files or propagate the information to the team (someone will do
it).

Personally, I will copy the proposal to the Avalon and Cocoon
development lists.  It seems that the proposal struck a couple
cords on this list, so we will see if the build scripts change :).

Jon Stevens wrote:
> 
> Please join the alexandria project's mailing lists. Gump, Maveric, JJAR,
> etc, are all trying to do this in one way or another.
> 
> I think that the first priority is to get CJAR* working. Once we have that,
> using the information provided by Gump to create standardized build files
> for projects becomes a whole lot easier.
> 
> * I like CJAR better than CJAN as a name now. CJAR == Comprehensive Jar
> Archive Repository.
> 
> -jon
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org