"Vincent Massol" <[EMAIL PROTECTED]> wrote on 19/09/2002 06:05:58 PM:
> > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: 19 September 2002 09:01 > > To: Turbine Maven Users List > > Subject: RE: Upgrade test plugin to JUnit 3.8.1 - Votes? > > > > "Vincent Massol" <[EMAIL PROTECTED]> wrote on 19/09/2002 05:22:53 PM: > > > > > What was changed in 1.1-snap from 1.0? Maybe we should deliver a 1.1 > > Changes: > > - added .cvsignore and navigation.xml to docs/. > > - added velocity.log and maven.log to .cvsignore > > - plugin:install goal added to maven.xml > > - plugin.jelly > > - bug fix where taskdef was left out of test:test > > - other system properties can now be passed to junit tests > > - junit jar now not in maven.home/lib, it's a dependency of the > plugin > > - test:single added, test:single-test deprecated > > - test:match added, test:match-test deprecated > > - project.properties maven.xdoc.date=left added > > - project.xml > > - logos fixed > > - gumpRepositoryId removed > > - url, siteDirectory, repository:connection, repository:url fixed > > - dependencies added > > - integrationUnitTestSourceDirectory and aspectSourceDirectory > removed > > BTW, that something that I would like to see in Maven: a changes page. > Same as what is done with Cactus for example: > http://jakarta.apache.org/cactus/changes.html#release_changes Got a proposed format, or just as an xdoc? > > The changelog page is not usable to see what has changed between two > versions. It is *possible* to use it in theory, but not adapted in > practice because there is too much noise. The changes to maven core lately have been few, it's the plugins where most of the activity is now, but i agree, changelog is busy. > > > final using junit 3.7 first and then move to junit 3.8.1 for > 1.2-snap? > > There's been enough change to go 1.1 now, IMHO. > > That's what I meant... We should do a 1.1 release now and then start the > 1.2-snap one. I'm happy to.....That makes 2 of us....someone else?? > > > How do we deliver a single plugin? Where does it show on the turbine > web > > > site what are the versions of the plugins delivered and where to > > > download them? Maybe we should drop them at ibiblio when we deliver > and > > Sounds like this should go in the plugin docs. > > Yes, there too. But I also think we need a global download page that > lists again all plugins with versions and links. In any case, we DO need > a "Download" link in Maven menu... This 'could' be generated as part of the plugin docs, using the <versions> of the pom, and added to http://jakarta.apache.org/turbine/maven/reference/plugins/index.html -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
