If you move the issue to the main project, the old issue url will
redirect. So you should move them, then close them in the new project
(if you want the redirect)
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 17, 2008 5:15 PM
To: Maven Developers L
On 18/02/2008, at 9:03 AM, Jeff Jensen wrote:
Possibly there are some to close (won't fix/won't do the
enhancement), but
what is the reasoning for a bulk close of all of them?
I think the reasoning is that they are all won't fix at this point -
but they should certainly be reviewed first.
Possibly there are some to close (won't fix/won't do the enhancement), but
what is the reasoning for a bulk close of all of them?
If consolidating all to one JIRA is of some benefit, then why not just bulk
move those not closed to the "new one" (after processing them per the
above)?
And consolida
Makes sense - let's sit on this for a bit to see if there are any
other objections and then can move forward.
On 18/02/2008, at 8:38 AM, Lukas Theussl wrote:
I thought maintenance mode also meant that people can still submit
patches to existing issues and we'll consider them.
However, gi
I thought maintenance mode also meant that people can still submit
patches to existing issues and we'll consider them.
However, given the small expected impact I think it would be most
practical to just close all open issues (plugins and core) as won't fix,
and install a consolidated jira wh
what does maintenance mode mean?
IMO, it would be that new issues can be reported, and are either fixed
or closed as "won't fix" because they are new work or non-critical. In
which case I would say:
- consolidate the projects (I'm not sure what this means in
practicality - I think you need
I wanted to propose that too, but what to do with the issues that are
open? As long as m1 is in maintenance mode, I think we should keep
reported issues visible. We could remove the 'create new issue' option
from all projects though and update the description to point to the new
jira to use.
+1. Gave it a spin on a big project, checked the licenses were in
place, scanned the commit logs.
On 16/02/2008, at 10:51 AM, Dan Fabulich wrote:
As you might expect, all the good bugs were found in 2.4.1 [looks
like some folks were waiting for SP1 to start testing... ;-)]
At least they
If the plugins are in the same state as the core, then I think that'd
be a good idea.
On 18/02/2008, at 7:57 AM, Brian E. Fox wrote:
What if all the maven 1.x jira projects where collapsed into one?
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Sunday, Februa
What if all the maven 1.x jira projects where collapsed into one?
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 17, 2008 3:34 PM
To: Maven Developers List
Subject: Re: JIRA for Maven 1.x?
If I'm not mistaken we didn't get a single critical bug re
On 18/02/2008, at 7:34 AM, Lukas Theussl wrote:
If I'm not mistaken we didn't get a single critical bug report after
1.1 was released. But that's not surprising, after all, it's a
perfect product... :)
I am not sure about closing the JIRAs, after all, maintenance mode
means that we still
The Parent POM section reads a bit confusingly because it uses "Ahead"
both times, but you've switched the order of the POMs :)
I'm trying to understand what the real scenario is where there is a
"child" POM that doesn't declare it's parent? Could that just be
declared as a build failure/wa
If I'm not mistaken we didn't get a single critical bug report after 1.1
was released. But that's not surprising, after all, it's a perfect
product... :)
I am not sure about closing the JIRAs, after all, maintenance mode means
that we still do accept bug reports, right? If anyone would submit
On Feb 15, 2008 4:51 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> As you might expect, all the good bugs were found in 2.4.1 [looks like
> some folks were waiting for SP1 to start testing... ;-)]
...
> Staging repo:
> http://people.apache.org/~dfabulich/staging-repo/
+1
I tested it with the Str
Hi,
Some questions for the guys that wrapped up Maven 1.1 :)
Since Maven 1.x is in maintenance mode, should most of the current
JIRAs that reflect things that won't be fixed be closed out?
At what point will we stop accepting new bugs?
And how does this affect the plugins - are they in the
maven-plugins (parent):
maven-site-plugin version should be 2.0-beta-6
It is already specified as 2.0-beta-6 in maven-parent.
maven-plugins overwrites this spec with "2.0-beta-5".
Benjamin Bentmann
-
To unsubscribe, e-mai
Vincent Siveton wrote:
Hi Dennis,
2008/2/16, Dennis Lundberg <[EMAIL PROTECTED]>:
Hi all
I'm going to release maven-parent-8 and when that is done
maven-plugins-11 (also a parent). Is there something more that should be
included before I go ahead with the releases?
Changelogs
maven-parent:
17 matches
Mail list logo
