Despite my comments on General@, I really like what maven offers. There
are some things that I would like to have in Maven or Centipede, so I
guess the best thing is to lend a hand. I have limited time, so I will
start with participating on the dev list. If I can manage code patches
I will send them here.
I already posted some possibilities for bootstrapping maven on the
Alexandria Dev list. I would like to know what is involved with
having separate repositories. IOW, to bootstrap Maven we would need
a repository with the working libraries we use--but to test maven
against the latest CVS of the dependancy libs we need to upload
the jars to a separate repository.
The build process for that would be something like this:
bootstrap-maven
+- download deps from known location
+- build dep jars
+- upload dep jars to new repository (i.e. working repository)
+- rebuild maven with new dep jars
That way Maven itself can avoid circular dependancies in GUMP,
and gain the benefit of early warnings if the dependancy libraries
change their interfaces.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
