Re: JIRA projects for m2 plugins?
I think it's also time to use the changes plugin. WDYT? On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > So what's the status on this? > > - Have we decided to create separate JIRA projects for m2 plugins? > - Can I create a Clover JIRA project the m2 clover plugin? I'd like to get > moving on this. > - Is there any recommendation for versioning the plugins? Should we start > at > 2.0 and simply increase the minor? Do plugins have to go through alphas, > betas, rcs or is it left at the discretion of the plugin contributors in > general? > > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::.
Re: JIRA projects for m2 plugins?
That sounds good. On 11/16/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > I have an idea: Why not ask Atlassian how they would best organize the > Maven 1 & Maven 2 project in JIRA? They should know what's the best solution > don't you think? > > -Vincent > > > -Original Message- > > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > > Sent: mercredi 16 novembre 2005 23:30 > > To: 'Maven Developers List' > > Subject: RE: JIRA projects for m2 plugins? > > > > > > > > I think we should vote to solve this asap, I believe these > > > are the options: > > > > > > [+1] create a new project for new m2 plugins, reuse m1 projects adding a > > new version > > > > Actually it could be the simplest way to do it. > > Users are already creating issues in m1 plugins and we move them in m2 > > land. > > We could create components in plugins : m1 plugin / m2 plugin ... > > It can help us to compare features in m1/m2 plugins > > The problem (which is not a rela one) is that we can have only one owner > > for a m1/m2 set of plugins. > > > > > [-1] create a new project for every m2 plugin > > Not before we have a separate Jira instance. > > > > > [+0] keep it as it's now > > > > Arnaud > > > > > > > > > > - > > 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 projects for m2 plugins?
I have an idea: Why not ask Atlassian how they would best organize the Maven 1 & Maven 2 project in JIRA? They should know what's the best solution don't you think? -Vincent > -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: mercredi 16 novembre 2005 23:30 > To: 'Maven Developers List' > Subject: RE: JIRA projects for m2 plugins? > > > > > I think we should vote to solve this asap, I believe these > > are the options: > > > > [+1] create a new project for new m2 plugins, reuse m1 projects adding a > new version > > Actually it could be the simplest way to do it. > Users are already creating issues in m1 plugins and we move them in m2 > land. > We could create components in plugins : m1 plugin / m2 plugin ... > It can help us to compare features in m1/m2 plugins > The problem (which is not a rela one) is that we can have only one owner > for a m1/m2 set of plugins. > > > [-1] create a new project for every m2 plugin > Not before we have a separate Jira instance. > > > [+0] keep it as it's now > > Arnaud > > > > > - > 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 projects for m2 plugins?
> > I think we should vote to solve this asap, I believe these > are the options: > > [+1] create a new project for new m2 plugins, reuse m1 projects adding a new > version Actually it could be the simplest way to do it. Users are already creating issues in m1 plugins and we move them in m2 land. We could create components in plugins : m1 plugin / m2 plugin ... It can help us to compare features in m1/m2 plugins The problem (which is not a rela one) is that we can have only one owner for a m1/m2 set of plugins. > [-1] create a new project for every m2 plugin Not before we have a separate Jira instance. > [+0] keep it as it's now Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA projects for m2 plugins?
haha okay - too early in the morning for me still. Kind regards, Dave Sag "Vincent Massol" <[EMAIL PROTECTED]> wrote on 16-11-2005 09:15:35: > This already exists, no need to vote on that. We're voting to change that > actually as it's not working (version issues). :-) > > > > -Vincent > > > > _ > > From: David Sag [mailto:[EMAIL PROTECTED] > Sent: mercredi 16 novembre 2005 09:03 > To: Maven Developers List > Subject: Re: JIRA projects for m2 plugins? > > > > > I would vote to make a new jira component within the maven 2 project for > each new plugin. > > Kind regards, > Dave Sag > > > > > > > [EMAIL PROTECTED] wrote on 15-11-2005 21:27:39: > > > I think we should vote to solve this asap, I believe these are the > options: > > > > [ ] create a new project for new m2 plugins, reuse m1 projects adding > > a new version > > [ ] create a new project for every m2 plugin > > [ ] keep it as it's now > > > > On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > So what's the status on this? > > > > > > - Have we decided to create separate JIRA projects for m2 plugins? > > > - Can I create a Clover JIRA project the m2 clover plugin? I'd like to > get > > > moving on this. > > > - Is there any recommendation for versioning the plugins? Should we > start at > > > 2.0 and simply increase the minor? Do plugins have to go through alphas, > > > betas, rcs or is it left at the discretion of the plugin contributors in > > > general? > > > > > > Thanks > > > -Vincent > > > > > > > > > - > > > 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 projects for m2 plugins?
Jason van Zyl a écrit : On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote: I think we should vote to solve this asap, I believe these are the options: [ ] create a new project for new m2 plugins, reuse m1 projects adding a new version [ ] create a new project for every m2 plugin +1 +1 Emmanuel [ ] keep it as it's now There is a good citizen aspect of this to consider. We'll flood the dashboard if we do this. Ideally I think a dedicated machine would be best and I think this can be done in a relatively short period of time. Vincent, will what we have now not work for you using a component? Also, I have fully automated manipulating JIRA via SOAP and I can create new projects quickly using that. So I can make all the projects once we decide what we're going to do. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA projects for m2 plugins?
This already exists, no need to vote on that. We're voting to change that actually as it's not working (version issues). :-) -Vincent _ From: David Sag [mailto:[EMAIL PROTECTED] Sent: mercredi 16 novembre 2005 09:03 To: Maven Developers List Subject: Re: JIRA projects for m2 plugins? I would vote to make a new jira component within the maven 2 project for each new plugin. Kind regards, Dave Sag [EMAIL PROTECTED] wrote on 15-11-2005 21:27:39: > I think we should vote to solve this asap, I believe these are the options: > > [ ] create a new project for new m2 plugins, reuse m1 projects adding > a new version > [ ] create a new project for every m2 plugin > [ ] keep it as it's now > > On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > So what's the status on this? > > > > - Have we decided to create separate JIRA projects for m2 plugins? > > - Can I create a Clover JIRA project the m2 clover plugin? I'd like to get > > moving on this. > > - Is there any recommendation for versioning the plugins? Should we start at > > 2.0 and simply increase the minor? Do plugins have to go through alphas, > > betas, rcs or is it left at the discretion of the plugin contributors in > > general? > > > > Thanks > > -Vincent > > > > > > - > > 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 projects for m2 plugins?
I would vote to make a new jira component within the maven 2 project for each new plugin. Kind regards, Dave Sag [EMAIL PROTECTED] wrote on 15-11-2005 21:27:39: > I think we should vote to solve this asap, I believe these are the options: > > [ ] create a new project for new m2 plugins, reuse m1 projects adding > a new version > [ ] create a new project for every m2 plugin > [ ] keep it as it's now > > On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > So what's the status on this? > > > > - Have we decided to create separate JIRA projects for m2 plugins? > > - Can I create a Clover JIRA project the m2 clover plugin? I'd like to get > > moving on this. > > - Is there any recommendation for versioning the plugins? Should we start at > > 2.0 and simply increase the minor? Do plugins have to go through alphas, > > betas, rcs or is it left at the discretion of the plugin contributors in > > general? > > > > Thanks > > -Vincent > > > > > > - > > 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 projects for m2 plugins?
My vote: create a new project for every m2 plugin. That said, I think it would be great to have a separate machine for that. Stéphane On 11/15/05, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > I think we should vote to solve this asap, I believe these are the > options: > > [ ] create a new project for new m2 plugins, reuse m1 projects adding > a new version > [ ] create a new project for every m2 plugin > [ ] keep it as it's now > > On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > So what's the status on this? > > > > - Have we decided to create separate JIRA projects for m2 plugins? > > - Can I create a Clover JIRA project the m2 clover plugin? I'd like to > get > > moving on this. > > - Is there any recommendation for versioning the plugins? Should we > start at > > 2.0 and simply increase the minor? Do plugins have to go through alphas, > > betas, rcs or is it left at the discretion of the plugin contributors in > > general? > > > > Thanks > > -Vincent > > > > > > - > > 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] > > -- .::You're welcome ::.
Re: JIRA projects for m2 plugins?
My vote > [x] create a new project for new m2 plugins, reuse m1 projects adding > a new version > [ ] create a new project for every m2 plugin > [ ] keep it as it's now > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA projects for m2 plugins?
> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: mercredi 16 novembre 2005 01:04 > To: Maven Developers List > Subject: Re: JIRA projects for m2 plugins? > > On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote: > > I think we should vote to solve this asap, I believe these are the > options: > > > > [ ] create a new project for new m2 plugins, reuse m1 projects adding > > a new version > > [ ] create a new project for every m2 plugin > > +1 +1 too > > [ ] keep it as it's now > > There is a good citizen aspect of this to consider. We'll flood the > dashboard if we do this. Ideally I think a dedicated machine would be > best and I think this can be done in a relatively short period of time. > > Vincent, will what we have now not work for you using a component? What we have now is a single Maven 2 project with components. So we're already using JIRA components. Not sure what you mean. > Also, I have fully automated manipulating JIRA via SOAP and I can create > new projects quickly using that. So I can make all the projects once we > decide what we're going to do. That's very cool. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA projects for m2 plugins?
On Tue, 2005-11-15 at 12:27 -0800, Carlos Sanchez wrote: > I think we should vote to solve this asap, I believe these are the options: > > [ ] create a new project for new m2 plugins, reuse m1 projects adding > a new version > [ ] create a new project for every m2 plugin +1 > [ ] keep it as it's now There is a good citizen aspect of this to consider. We'll flood the dashboard if we do this. Ideally I think a dedicated machine would be best and I think this can be done in a relatively short period of time. Vincent, will what we have now not work for you using a component? Also, I have fully automated manipulating JIRA via SOAP and I can create new projects quickly using that. So I can make all the projects once we decide what we're going to do. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org believe nothing, no matter where you read it, or who has said it, not even if i have said it, unless it agrees with your own reason and your own common sense. -- Buddha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA projects for m2 plugins?
I think we should vote to solve this asap, I believe these are the options: [ ] create a new project for new m2 plugins, reuse m1 projects adding a new version [ ] create a new project for every m2 plugin [ ] keep it as it's now On 11/15/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > So what's the status on this? > > - Have we decided to create separate JIRA projects for m2 plugins? > - Can I create a Clover JIRA project the m2 clover plugin? I'd like to get > moving on this. > - Is there any recommendation for versioning the plugins? Should we start at > 2.0 and simply increase the minor? Do plugins have to go through alphas, > betas, rcs or is it left at the discretion of the plugin contributors in > general? > > Thanks > -Vincent > > > - > 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 projects for m2 plugins?
I am ready to check in the Weblogic Plugin. I think it makes sense to create new projects for these plugins since the structure will be quite different. This also allows us to keep maintaining the version 1.0 plugins as well. I woiuld prefer that we start with 2.0 for a number of reasons since I want to keep maintaining the 1.0 plugin for a while as well. I plan on having an alpha and beta version since I am discovering some new ideas with the advent of the native Java option as well as new interaction with the container. Do we want one main maven2 project with sub projects under that or should we create a maven2 directory under each project? I too would like to get my code into the repository ASAP. Looking forward to everyone's input. Scott D. Ryan Chief Technology Officer Soaring Eagle LLC. 9742 S. Whitecliff Place Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 1:58 AM To: 'Maven Developers List' Subject: JIRA projects for m2 plugins? So what's the status on this? - Have we decided to create separate JIRA projects for m2 plugins? - Can I create a Clover JIRA project the m2 clover plugin? I'd like to get moving on this. - Is there any recommendation for versioning the plugins? Should we start at 2.0 and simply increase the minor? Do plugins have to go through alphas, betas, rcs or is it left at the discretion of the plugin contributors in general? Thanks -Vincent - 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]
