My biggest complaint right now is with the way we are doing things and how much duplication we now have (and will have in the future) wrt maven and ant configuration. Each subproject has it's own copy of project.properties, maven.xml, and 90% of each project.xml is repeated. I've already wasted several hours trying to get these all in sync. I am -1 for keeping each separate for the sake of seperation.
I prefer that we setup our maven project files to extend a single top project.xml under current/site/ (future), like it is done now in commons. This includes the CheckStyle config and license as well as other shared resources.
I think this is reasonable, but I'm not totally thrilled about the fact that you then cannot build the distributions with Maven. Also, I don't use "current", although maybe I should, but I think it would then be annoying that the relative paths to the shared files only works in one of two possible SVN states.
I don't mean to say that it's better to have copies all over the place, but these are things that have frustrated me about our options.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
