> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 12 November 2003 22:34 > To: 'Maven Developers List' > Subject: RE: maven-new > > > I say we entirely separate out the plugins into their > > own JIRA projects and then take a look at what's really in > > the core. > > Not much left! :) > > > I can live with releasing what we have now as 1.0. > > > > Well, I disagree for a few reasons. These are just my opinion though, of > course. > - 1.0 will get more publicity, and it might be the time users who were > bitten by problems such as the leak come back and give it another shot. > It'd > be nice for it to work for them this time around :)
I agree here. Fixing the memory leak is a must for 1.0. > - 1.0 will still need to bundle the optional plugins in some way (or maybe > we use the NSIS installer to selectively download them? :) Either that or some installer plugin that lists all the plugins as dependencies. Thus someone who installs maven can call: "maven installer:plugins" (or something like that) to get them downloaded and installed automatically. We should definitely use the latest releases for the versions to use. Actually, we could periodic updates of this plugins, with latest versions of plugins so that people can easily download them all at once... Another solution is simply to provide a batch file/script that contains: maven plugin:download -DgroupId=maven -DartifactId=maven-changes-plugin -Dversion=X.Y maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=X.Y maven plugin:download -DgroupId=maven -DartifactId=maven-ear-plugin -Dversion=X.Y [...] Actually, I can easily create a new goal in the multichanges plugin to generate this kind of script as I have all the information I need there. I'll give this a try! > So any major > bugs > in them need to be fixed and up to release status. However I agree here - > lets push to get each plugin we release with 1.0 to a stable release. They > can keep going beyond that, but we can at least say "we can use x for > 1.0". see http://maven.apache.org/reference/plugins/optional/multichanges-report.h tml for some good overview of the state of plugin releases. Everything that is before 2003-09-29 has not been redelivered since Maven 1.0 rc1. > It may be the case that this is already there. > - the memory usage improvement is huge, and speed can be further improved > within the current refactoring by more efficient plugin loading. This is > going to be important for anyone generating a multiproject site with lots > of > reports (a very common usage). > - I think the people that don't care about polish are using it now anyway, > so the version, as Jason said, is irrelevant. > - On the contrary, if we release it as 1.0, we probably find we need to > rush > a 1.1 to fix the same bugs we currently have waiting for 1.0. > > When it comes down to it, the answer is "what's in a name?" :) I think what's important is to do frequent releases. An rc2 release very soon would be most welcome I think (it would be nice if it has the memory leak fix... not sure what the status is). The problem with 1.0 is that we've already been waiting too long... Everyone is now waiting for THE 1.0 version. I agree with Brett that we need to: - include the memory bug fix - make Maven fast > > But where we stand is that there's either this reasonable amount of work > waiting for 1.0, or there's nothing. We either release 1.0 now (After a > quick review of JIRA), or commit to getting the fixed up plugin context > code > into that release and have two more release candidates. > > One argument in favour of releasing now is that HEAD can open up for new > development such as the recent POM suggestions being made. However, there > is > nothing stop that in the current scenario either - it just means > everything > targetted at 1.0 including core bugfixes goes onto the branch. > > Thoughts? See above... :-) Thanks -Vincent > > Cheers, > Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
