Hi Sam,
Here are a couple more ideas as I'm looking at what I did a couple months
ago.
1) Could we make the whole process an Ant task?
2) Project descriptors need to be normalized, the project file is really a
set of targets. Right now there is a top level project and nested projects
in a project XML descriptor. I would like to be able to readily convert the
XML descriptors into java objects and this makes it difficult. So the
project XML descriptor should actually look more like the build.xml file for
a project. Maybe we could eventually move toward using a projects build.xml
file for the descriptor if we got a little more standard.
3) Allow a directory with overriding repository descriptors, so that your
customized configuration matches the form of the anonymous access repository
descriptors. Again so that it's easier to convert the XML to a Java object.
4) Use ${lib.repo} as defined in ~/build.properties as the place to look for
external jar files so that we can remove that info from the workspace.
5) Make it so that updating the gump repository doesn't affect a local setup
so that I can get any new dependency information and just build again.
I could easily finish the xml->java digesters (the commons digester), and
than it is very easy to deal with the system in a very convenient way. I
also have a dependency engine that geir built for me that determines the
correct build order.
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
