Hi, Just thought I would try to squeeze out a couple thoughts before I take off (yes, I will really leave at some point :-)).
o Restoring update-jars or cleaning up the naming of the JAR files. I removed update-jars and replaced it with an automated update facility but it won't work for JARs that don't have a differentiating name. This is all part of the theory that all JARs should be uniquely identified even if it is a CVS dev snapshot. And the differentiation has to be at the resource level or the JAR not the storage level like CVS. I don't want to have to rely on the storage mechanism for versioning. Anyway either someone can restore the update-jars or do the grand JAR renaming. o I mentioned Quartz as something that could be integrated with the Reactor generator to make a real Reactor that performs timed builds. The package looks decent, only tried the example, but it has a crontab parser it's all Java so it would be cool to integrate. Someone could try to Mavenize his project to try and get him involved :-) Another option is to try and use a TimerMBean and integrate JMX but this might be a bit much. But there is a timer implementation in the mx4j distribution. But I think quartz might be a better option. o Javadoc needs the classpath so that the references are resolved correctly. Is that just the 'bootclasspath' option? Using the classpath reference doesn't seem to do anything. o Someone could drop a line to the JPackage folks who are trying to create standard RPMs for Java packages. The info in the POM would probably be a perfect source of information for making the RPMs and I know that Josh has a task for this. So I'm sure between Josh and the JPackage folks we could include RPMs to the repository. o A mechanism (and target in the build files) is needed to push the project descriptor up to the shared location. We can use the turbine projects as a test for now because enough of us have ssh access to push the project descriptors up. But we will probably have a 'more public' location. I was thinking of possibly using the httpclient package from the commons along with SSL to create a general secure transfer mechanism for pushing all the Maven artifacts around. Maybe each project could make a self-signed cert they could register and use that to sign their distribution artifacts and transfer any arbitrary project artifacts. I am trying to make the reactor generator smarter so that it can just suck in all project descriptors in a repo and make a reactor from it. The equivalent of a gump build. And as Maven is used by more projects the build will become more complete. It will definitely be a sure sign of whether Maven is actually useful or not. That's all I can think of for now. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org
