Yes, I've actually always agreed with applying the development mode option. So this bug fix will wait for the next release, there's definitely no problem.
Let's release! +1 :-) On 11/28/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 28 Nov 06, at 4:00 AM 28 Nov 06, Fabrice Bellingard wrote: > Hi John, > > what about the issue "http://jira.codehaus.org/browse/MWAR-60";? > At the time I commented the issue, I expected some other people to > give > their point of view on that before working on it. IMHO, this > represents a > bug that is a regression between 2.0 and 2.0.1, and therefore that > needs to > be fixed before 2.0.2 is released. > What do you think of this? > So if we were to generalize this is really a development mode option versus a production mode option? I'm all for helping with developer productivity and applying this development mode stuff is important. As for this version unless you're going to fix it, it's going to hold up the release and in the grand scheme of thing the issue only has one vote and pretty far down in the ranking according to users: http://repo1.maven.org/reports/plugins/plugin-issues.txt I think we should release, and then if you want to fix that issue we can turn around and release again next week. In the future we'll have to update the roadmap accordingly, as there should be unresolved issues in the roadmap when the vote is cast. Jason. > Fabrice. > > On 11/28/06, John Tolentino <[EMAIL PROTECTED]> wrote: >> >> Hi Everyone, >> >> The latest version (2.0.2-SNAPSHOT) of the maven-war-plugin is now >> deployed to the snapshot repo. We'll also have the license stuff >> resolved before doing any release. >> >> For your reference of features included in this release: >> >> http://www.nabble.com/Planning-a-release-of-Maven-War-Plugin- >> tf2714187s177.html >> >> I now like to call a vote for Releasing the Maven WAR Plugin. >> >> Here's my +1. >> >> Thanks, >> John
