----- Original Message ----- From: "Henri Yandell" <[EMAIL PROTECTED]> > Responding to advice, I've decided to request for comments here before > scaring the Commons list again. > > I've some questions on how to integrate the Mavenising of Commons into > Commons. The following is my current suggestion, but I'm not expecting it > to be the final form of what happens, I just want to play What If. > > Mavenising: > =========== > > Choose a version of Maven to begin using as standard. Undergo upgrades as > a concerted effort. The version of Maven would be either b4 or b5 > depending on release date of b5 and time in which Commons starts to move. > This becomes less of problem when Maven stabalises and gets with the > update thing. Would also have to make sure that the version chosen had a > nicely snapshotted documentation set which new Commons developers could be > pointed to. > > Add project.xml to all projects. > > It would be nice to have a project.properties that all projects could > share as they'd share a common, possibly Commons unique, theme. But more > likely we'd just have a project.properties in each dir.
Maybe we could have a project.properies in jakarta-commons and in the project's directory, then a project can provide specific properties while inheriting common stuff. > Nightly build. The websites would build nightly, as would the downloads. Super cool! > Currently the website doesn't integrate the download, so would need to > solve that before going live with Commons. Agreed. > Repository. Does Commons run its own repository or use the Maven one. How > would the management of this work. [I assume there are lots of ideas of > this in peoples heads, really I'm just fishing to see what the next steps > for lib.repo are and how Commons can fit into them as a user]. Reusing the same Maven repo would make sense, or at least populating the maven one with the latest-greatest development builds of commons projects for those on the bleeding edge. > Reporting. The nightly build would need to report on success/failure etc. > What is the current gump integration status, would this be the choice for > a nightly build, or is it preferred to use a simple shell script > currently. Maybe when the reactor stuff gets going, we could treat the whole of jakarta commons as one reactor project; then start to experiment with Maven's continuous integration features to provide a neat alternative to gump? James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
