Re: Releasing our parent POMs
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: https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=628267&r2=587312&diff_format=h For maven-parent, I would like to see more archives for ML like nabble or markmail. Feel free to add more... maven-plugins (parent): https://svn.apache.org/viewvc/maven/plugins/trunk/pom.xml?r1=618649&r2=587343&diff_format=h maven-site-plugin version should be 2.0-beta-6 It is already specified as 2.0-beta-6 in maven-parent. PS. I will pull back maven-plugin-plugin to version 2.3 in maven-plugins before the release, and then bump it back to 2.4-SNAPSHOT again when the release is done. I want to see maven-plugin-plugin release before releasing maven-plugins-parent. We did several major changes since the last release (around 1 year) and only one issue is left. I'd feel more comfortable if maven-plugin-plugin 2.4 has been tried on at least one other release before we add it to the parent. We can always make another release of the plugins parent later on. Cheers, Vincent -- Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing our parent POMs
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-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JIRA for Maven 1.x?
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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: atypical plugin use cases
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/warning? I think modules really needs to
reflect the hierarchical relationship - and it's an easier problem to
attack than to change the order if that scenario is used.
With regards to the assembly - we probably need to look at some
alternative ways to attack that problem.
For me, the main things I think we should focus on with plugin
lifecycle are:
- assembly lifecycle (perhaps related to the aggregator changes you
propose)
- decent integration of code coverage plugins (we never got this
forked lifecycle quite right)
I'm not sure about the aggregator changes - I realise the problems you
describe, but will need to give it more thought - I think more digging
on the proposed solutions will be needed, referring to an example as I
had trouble visualising it from your description (I may just need more
coffee :).
Build introspection is a good thing, some thoughts:
- this would enable guarded mojo execution too
- I don't think legacy mojos is a big deal - you just miss some
information you never had - just need to make sure that things assume
the information is always partial (since plugin devs will be lazy
sometimes too) - as long as it still provides correct results (or
correct based on knowledge given) I think this is ok.
- I think annotations are a good idea, possibly with additional
interfaces so that you can code the conditional logic necessary if the
annotations don't suffice (so, a combo of the two proposals)
- I think an alternative way to look at this might be to structure
mojo execution such that you can essentially run it in dry run (so you
can run the whole build, just not affect anything). This would
unfortunately significantly affect mojo design, however - but worth
thinking about how it might help for the more complicated logic cases.
Given all this, I think the 3 proposals can actually be split up into
separate documents.
Thanks John!
Cheers,
Brett
On 14/02/2008, at 9:34 AM, John Casey wrote:
Hi,
I'm trying to document some of the design problems with sort of
exotic plugin use cases, things like aggregation and use of $
{reactorProjects}, that we're running into under the current setup.
I have proposals to address most of the issues, but I'd love to hear
what you would propose...or even tell me about plugin-design issues
that I haven't thought of.
I'd really like to take a whack at the bigger problems for 2.1, but
if that doesn't happen, 2.2 is a fine target for me, as long as we
start the discussion now. We have a lot of experience with what
works and what doesn't from 2.0.x, so let's take advantage of that
to see what we got wrong, and how we can correct it.
The page is here:
http://docs.codehaus.org/display/MAVEN/Atypical+Plugin+Use+Cases
Thanks in advance,
-john
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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 do accept bug reports, right? If anyone would submit a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. Makes sense - but how about closing out the issues that are left open that won't be fixed? I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. Do you have permissions to do that already? -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Surefire version 2.4.2
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 Struts 1 and Struts 2 builds and websites, and spot-checked the gpg signatures. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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. -Lukas 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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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 to keep a project open but remove *all* of it's permissions for the old issue links to redirect to their new home) - close out any open issues that aren't going to be fixed - leave permissions as is for the consolidated project. Cheers, Brett On 18/02/2008, at 8:12 AM, Lukas Theussl wrote: 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. -Lukas 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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA for Maven 1.x?
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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: > 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 same state? > > Thanks! > > Cheers, > Brett > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Surefire version 2.4.2
+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 must be learning to pin their versions :) We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=14062 There are still 44 issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10541&status=1 Staging repo: http://people.apache.org/~dfabulich/staging-repo/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sr. Director Product Development Exist Global [EMAIL PROTECTED] http://blogs.exist.com/bporter http://www.exist.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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 where people can still report new or re-open old issues if they want them fixed. Cheers, -Lukas Brett Porter wrote: 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 to keep a project open but remove *all* of it's permissions for the old issue links to redirect to their new home) - close out any open issues that aren't going to be fixed - leave permissions as is for the consolidated project. Cheers, Brett On 18/02/2008, at 8:12 AM, Lukas Theussl wrote: 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. -Lukas 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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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, 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 where people can still report new or re-open old issues if they want them fixed. Cheers, -Lukas Brett Porter wrote: 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 to keep a project open but remove *all* of it's permissions for the old issue links to redirect to their new home) - close out any open issues that aren't going to be fixed - leave permissions as is for the consolidated project. Cheers, Brett On 18/02/2008, at 8:12 AM, Lukas Theussl wrote: 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. -Lukas 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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
RE: JIRA for Maven 1.x?
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 consolidating to one - I'd like to see arguments on it. So far, the 3 of you are easily for doing it, but I am not sure of the "real benefit". I have some thoughts on the pros, but some cons too! :-) -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Sunday, February 17, 2008 3:39 PM To: Maven Developers List Subject: Re: JIRA for Maven 1.x? 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 where people can still report new or re-open old issues if they want them fixed. Cheers, -Lukas Brett Porter wrote: > 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 to keep a project open but remove *all* > of it's permissions for the old issue links to redirect to their new home) > - close out any open issues that aren't going to be fixed > - leave permissions as is for the consolidated project. > > Cheers, > Brett > > On 18/02/2008, at 8:12 AM, Lukas Theussl wrote: > >> 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. >> >> -Lukas >> >> >> 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, >>> 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 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 a >>> patch or report something critical, I would still be willing to >>> apply/fix it and do a release. But given the late activity, this is >>> not likely to happen. >>> I'd agree to close the sandbox plugins, I wanted to do that myself >>> already a long time ago. >>> -Lukas >>> Brett Porter wrote: >>> 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA for Maven 1.x?
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. 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)? Yeah, that might make more sense thinking about it. You want to keep the roadmap/release notes for the old plugins releases, right? And consolidating to one - I'd like to see arguments on it. So far, the 3 of you are easily for doing it, but I am not sure of the "real benefit". I have some thoughts on the pros, but some cons too! :-) Easier management if it is to be used going forward, much cleaner interface for people filing bugs at codehaus :) - Brett -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Sunday, February 17, 2008 3:39 PM To: Maven Developers List Subject: Re: JIRA for Maven 1.x? 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 where people can still report new or re-open old issues if they want them fixed. Cheers, -Lukas Brett Porter wrote: 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 to keep a project open but remove *all* of it's permissions for the old issue links to redirect to their new home) - close out any open issues that aren't going to be fixed - leave permissions as is for the consolidated project. Cheers, Brett On 18/02/2008, at 8:12 AM, Lukas Theussl wrote: 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. -Lukas 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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: 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 same state? Thanks! Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ --
RE: JIRA for Maven 1.x?
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 List Subject: Re: JIRA for Maven 1.x? 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. > > > 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)? Yeah, that might make more sense thinking about it. You want to keep the roadmap/release notes for the old plugins releases, right? > > > And consolidating to one - I'd like to see arguments on it. So far, > the 3 > of you are easily for doing it, but I am not sure of the "real > benefit". I > have some thoughts on the pros, but some cons too! :-) Easier management if it is to be used going forward, much cleaner interface for people filing bugs at codehaus :) - Brett > > > > -Original Message- > From: Lukas Theussl [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 17, 2008 3:39 PM > To: Maven Developers List > Subject: Re: JIRA for Maven 1.x? > > > 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 where people can still report new or > re-open old issues if they want them fixed. > > Cheers, > -Lukas > > > Brett Porter wrote: >> 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 to keep a project open but remove >> *all* >> of it's permissions for the old issue links to redirect to their new > home) >> - close out any open issues that aren't going to be fixed >> - leave permissions as is for the consolidated project. >> >> Cheers, >> Brett >> >> On 18/02/2008, at 8:12 AM, Lukas Theussl wrote: >> >>> 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. >>> >>> -Lukas >>> >>> >>> 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, 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 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 a patch or report something critical, I would still be willing to apply/fix it and do a release. But given the late activity, this is not likely to happen. I'd agree to close the sandbox plugins, I wanted to do that myself already a long time ago. -Lukas Brett Porter wrote: > 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 same state? > > Thanks! > > Cheers, > Brett > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> ---
