Ok, some answers from my pov: 0) Shared project.properties? Maybe, maybe not.... 1) I'd rather b5 but since it's not out....b4 will have to do. 2) Any suggestions on who/how the nightly build would be done? How is it done now? 3) I'd stick with the existing repository that maven is using. 4) Success failure could be integrated into maven's build process. The current Gump integration last I knew was that Stefan had gotten Maven to bootstrap and was working at letting Gump use maven for builds. Stefan? -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers
Henri Yandell <[EMAIL PROTECTED]> 06/22/02 03:50 PM Please respond to "Turbine Maven Users List" To Turbine Maven Users List <[EMAIL PROTECTED]> cc bcc Subject Maven in Commons 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. Nightly build. The websites would build nightly, as would the downloads. Currently the website doesn't integrate the download, so would need to solve that before going live with Commons. 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]. 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. That's the list at the moment. I'm missing tons I'm sure. Hen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
