Hi Nicola, given how much discussion is currently going on @ Krysalis about autogenerating the build file for the user, and how much doco there is on cents, this is an unusual post.
Lets see: - We're not talking about autodownloading plugins here. - Cents don't have an autogenerated init target(?) - There is no common delegator file in Centipede(?) If I could get centipede to work under linux I might bother using it. But, as usual, I'm too dumb to use one of your tools. > We offered to merge efforts in a single new project in a discussion at > Jakarta General, but some developers simply said no. > Is this "copying" what you want to do? > We have integrated Maven documentation generation in Centipede since our > last beta, and give you due credit. The extent of your documentation on maven in Centipede at http://krysalis.sourceforge.net/centipede/centipede/maven-cent.html is vast. As a maven developer, it stuns me that's all you can come up with. Not even a single link to the maven site. And if I remember correctly, I'm the one that started the discussion on the krysalis list. It didn't get far, though. > You are free to do it, but I just wanted to tell the Maven community what is > happening. And me posting to the dev list is hiding it somehow? I've tried to read your documentation, and understand how things work. You make it too hard. I told you that 2 months ago, and now you're starting to document stuff? According to the forest developers (which Centipede uses) "Forrest isn't ready for prime time yet,". There's no site, no docs and hence I've gotten nowhere with it. Since that's your documentation system (something I'm interested in), I thought that would be a good place. You'd think you'd be happy we were converging. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers From: <[EMAIL PROTECTED]> > We've been talking about this for a while, but it's time to make it happen > sooner rather than later. > > Here's the basic plan we discussed this morning (my time). > > Goals > - Allow plug-ins to be added more easily by the user > - Allow user to keep their build file the way they want > > Details: > - Plugins are jars with the following contents: plugin.properties, > plugin-build.xml, plugin-delegators.xml > - User downloads plugins and copies them to ${maven.home}/plugins > - The user can tell maven about the plugins by doing: ant > maven:install-plugins > - This process: 1) scans the plugins directory comparing jars to > directories, ala Tomcat with WARs and webapps > - 2) unzips any 'new' plugins > - 3) runs a task to parse the init target and produce > the callbacks > - 4) runs a task to regenerate a proposed new file - > delegators.xml with all targets that may be > delegated to in all available plugins and 'core > maven' > - The user adds a delegator to thier build file, e.g. maven:j2ee:war, or > the install offers to do it for them(?), and they call it as usual. > > The 'install' process could be placed as part of the 'verify-project' step > as well, so that if the user ran ANY existing maven target, it would do > it's work. This quite a nice description of what Krysalis Centipede http://www.krysalis.org/centipede/ offers since some weeks now, and the Apache Poi project uses this autodownload feature (that uses JJAR BTW) to build the site with a cron script every 2 hours. We offered to merge efforts in a single new project in a discussion at Jakarta General, but some developers simply said no. Is this "copying" what you want to do? We have integrated Maven documentation generation in Centipede since our last beta, and give you due credit. You are free to do it, but I just wanted to tell the Maven community what is happening. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- 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]>
