t;...
>
> Kind regards
> Karl Heinz Marbaise
>
> On 18/08/17 20:52, Karl Heinz Marbaise wrote:
> > Hi to all,
> >
> > I have realized that in MASSEMBLY it is possible to define an issue Type
> > "Dependency Upgrade" which is very feasible for our p
Hi to all,
I have realized that in MASSEMBLY it is possible to define an issue Type
"Dependency Upgrade" which is very feasible for our projects...
So I have asked INFRA[1] if we could have that for our other JIRA
projects as wellSo the now we can decide between three options:
A
e asked INFRA[1] if we could have that for our other JIRA projects
> as wellSo the now we can decide between three options:
>
>
> A) switch your other schemes to match MASSEMBLY - meaning in addition to
> getting 'Dependency Upgrade' you also get add additional 30+
le for our projects...
So I have asked INFRA[1] if we could have that for our other JIRA
projects as wellSo the now we can decide between three options:
A) switch your other schemes to match MASSEMBLY - meaning in addition
to getting 'Dependency Upgrade' you also get add additiona
;
> >> Hi to all,
> >>
> >> I have realized that in MASSEMBLY it is possible to define an issue
> >> Type "Dependency Upgrade" which is very feasible for our projects...
> >>
> >> So I have asked INFRA[1] if we could have that for our oth
r our projects...
So I have asked INFRA[1] if we could have that for our other JIRA
projects as wellSo the now we can decide between three options:
A) switch your other schemes to match MASSEMBLY - meaning in addition
to getting 'Dependency Upgrade' you also get add additional
18 Aug 2017 20:52:55 +0200, Karl Heinz Marbaise
wrote:
Hi to all,
I have realized that in MASSEMBLY it is possible to define an issue Type
"Dependency Upgrade" which is very feasible for our projects...
So I have asked INFRA[1] if we could have that for our other JIRA
proje
Hi to all,
I have realized that in MASSEMBLY it is possible to define an issue Type
"Dependency Upgrade" which is very feasible for our projects...
So I have asked INFRA[1] if we could have that for our other JIRA
projects as wellSo the now we can decide between three opt
here is the precise list of Jira projects we'll migrate:
https://github.com/khmarbaise/jira-asf-migration/blob/master/project.list
Regards,
Hervé
Le jeudi 8 janvier 2015 11:42:54 Stephen Connolly a écrit :
> The JIRA projects for the mojo plugins will stay with mojo at codehaus. The
&
nd lock the projects.
> >> New issues go into ASF JIRA. We triage all the open issues in codehaus's
> >> JIRA and recreate issues on ASF JIRA where we are not rejecting the
> >> codehaus issue.
> >>
> >>> > > and how to get Codehaus content? An
The JIRA projects for the mojo plugins will stay with mojo at codehaus. The
move is only for the ASF hosted code related projects
On 8 January 2015 at 11:29, Lennart Jörelid
wrote:
> Sounds nice.
>
> Presumably, we can retain JIRA admin privileges for the current CodeHaus
> projec
aven dev with knowledge and
> >> karma?
> >> >
> >> > You will need someone with the Jira Systems Admin privilege to do the
> >> > export for you.
> >> >
> >> > > I'm interested to try the process on MPLUGIN [1]
> >&
> > You will need someone with the Jira Systems Admin privilege to do the
>> > export for you.
>> >
>> > > I'm interested to try the process on MPLUGIN [1]
>> > > then be ready for later any Mave developer to do the same for each and
>> >
; > I'm interested to try the process on MPLUGIN [1]
> > > then be ready for later any Mave developer to do the same for each and
> > > every Jira project
> > >
> > > notices:
> > > 1. account dedup will have to work when executed multiple times, since
> a
do the
> export for you.
>
> > I'm interested to try the process on MPLUGIN [1]
> > then be ready for later any Mave developer to do the same for each and
> > every Jira project
> >
> > notices:
> > 1. account dedup will have to work when executed mult
later any Mave developer to do the same for each and
> > every Jira project
> >
> > notices:
> > 1. account dedup will have to work when executed multiple times, since a
> > lot of accounts are shared between Maven Jira projects
> > 2. I still didn't underst
hat allow us to take an XML
backup of the full system.
>
> > I'm interested to try the process on MPLUGIN [1]
> > then be ready for later any Mave developer to do the same for each and
> every
> > Jira project
> >
> > notices:
> > 1. account dedup will ha
;
> notices:
> 1. account dedup will have to work when executed multiple times, since a lot
> of accounts are shared between Maven Jira projects
Understood.
> 2. I still didn't understand: will the Jira issue identifiers change or not?
> Will Codehaus MPLUGIN-288 migrate to MPLU
ce a lot
> of accounts are shared between Maven Jira projects
> 2. I still didn't understand: will the Jira issue identifiers change or not?
> Will Codehaus MPLUGIN-288 migrate to MPLUGIN-288 in ASF or is there a risk
> that it changes?
>
> Regards,
>
> Hervé
>
> [1]
count dedup will have to work when executed multiple times, since a lot
of accounts are shared between Maven Jira projects
2. I still didn't understand: will the Jira issue identifiers change or not?
Will Codehaus MPLUGIN-288 migrate to MPLUGIN-288 in ASF or is there a risk
that it changes
29, 2014 at 2:10 AM, Hervé BOUTEMY wrote:
>>> Le dimanche 28 décembre 2014 21:18:18 David Nalley a écrit :
>>>> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
>>>>
>>>> wrote:
>>>>> Dear Infra,
>>>>>
>>>>
you export, the better.
Mark
>
> On Mon, Dec 29, 2014 at 2:10 AM, Hervé BOUTEMY wrote:
>> Le dimanche 28 décembre 2014 21:18:18 David Nalley a écrit :
>>> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
>>>
>>> wrote:
>>>> Dear Infra,
>>
Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
>>
>> wrote:
>> > Dear Infra,
>> >
>> > For historical reasons, the Maven project has a host of JIRA projects
>> > at codehaus. This is not an ideal situation for many reasons.
>> >
&g
Le dimanche 28 décembre 2014 21:18:18 David Nalley a écrit :
> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
>
> wrote:
> > Dear Infra,
> >
> > For historical reasons, the Maven project has a host of JIRA projects
> > at codehaus. This is not an
t;> For historical reasons, the Maven project has a host of
> JIRA projects
> >> at codehaus. This is not an ideal situation for many reasons.
> >>
> >> In the past, discussions on moving onto ASF infrastructure have
> >> founded on the sheer number: dozens
On Sun, Dec 28, 2014 at 9:18 PM, David Nalley wrote:
> On Sat, Dec 27, 2014 at 11:37 AM, Benson Margulies
> wrote:
>> Dear Infra,
>>
>> For historical reasons, the Maven project has a host of JIRA projects
>> at codehaus. This is not an ideal situation for m
e SQL level, which, I think, would at least involve
> collaboration.
>
> Can all the maven jira
>> projects share a common group of project admins, contributors, etc or is
>> each unique?
>
> I believe that the answer is that they will all club together. All the
> Maven p
Margulies
> wrote:
>>
>> Dear Infra,
>>
>> For historical reasons, the Maven project has a host of JIRA projects
>> at codehaus. This is not an ideal situation for many reasons.
>>
>> In the past, discussions on moving onto ASF infrastructure have
>&
On 27-Apr-08, at 11:56 AM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
> When should users go to the JIRA project and when to the wiki?
Those should be collapsed too and just put in the wiki.
OK, I just edited the project description to redirect people over to
Confluence. Can we disable
Jason van Zyl wrote:
> When should users go to the JIRA project and when to the wiki?
Those should be collapsed too and just put in the wiki.
OK, I just edited the project description to redirect people over to
Confluence. Can we disable the creation of new issues for MNGFAQ?
Benjamin
Just move all the old issues (even closed ones) and then the old issue
numbers should redirect.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 27, 2008 11:31 AM
To: Maven Developers List
Subject: Re: Organization of JIRA projects
On 27-Apr-08, at 8
e
referring to the ITs?
No, I meant
http://maven.apache.org/issue-tracking.html
and the section "Maven Project Administration". The majority of
people visiting this page are usually Non-PMCs and don't need to
know about MPA. The less JIRA projects we offer to select, the
s
e confluence landing page referring
to the ITs?
No, I meant
http://maven.apache.org/issue-tracking.html
and the section "Maven Project Administration". The majority of people
visiting this page are usually Non-PMCs and don't need to know about MPA.
The less JIRA projects we o
On 27-Apr-08, at 6:46 AM, Benjamin Bentmann wrote:
Hi,
this thread is somehow extending the discussion about "Where to
create JIRA
issues for Maven documentation?" [0] and seeks to clarify the intended
target JIRA project for new issues, especially those projects listed
in the
category "M
Hi,
this thread is somehow extending the discussion about "Where to create JIRA
issues for Maven documentation?" [0] and seeks to clarify the intended
target JIRA project for new issues, especially those projects listed in the
category "Maven Admin".
For example, the recent issue MNG-3551 is abo
... and DOAP, and GPG, and invoker, and a bunch of project categories.
On 23/01/2007, at 7:53 AM, Brett Porter wrote:
I've fixed the permissions schemes so this goes to
issues@maven.apache.org where it belongs. I've also added the
released 1.0-alpha-1 version and the under development 1.0-al
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Brett Porter closed MPA-36:
---
Assign To: Brett Porter (was: Vincent Massol)
Resolution: Fixed
> associate Maven svn with JIRA projects
> --
>
>
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Jason van Zyl updated MPA-36:
-
Fix Version: 2006-q1
> associate Maven svn with JIRA projects
> --
>
> Key: MPA-36
> URL: http://ji
url.6=http://svn.apache.org/viewcvs.cgi/maven
I think this is fine. We can turn it off if there are any performance concerns.
> associate Maven svn with JIRA projects
> --
>
> Key: MPA-36
> URL: http://jira.codehaus.org/browse/MPA
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Vincent Massol updated MPA-36:
--
Attachment: subversion-jira-plugin.properties
> associate Maven svn with JIRA projects
> --
>
> Key: MPA-36
&g
associate Maven svn with JIRA projects
--
Key: MPA-36
URL: http://jira.codehaus.org/browse/MPA-36
Project: Maven Project Administration
Type: Task
Components: issue management
Reporter: Brett Porter
Assigned to: Vincent
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
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 w
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 m
>
> 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 l
27;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 wo
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
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 proje
or 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 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?
> &g
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
> -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 w
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
> 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
ECTED]
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
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 in
On Tue, Aug 09, 2005 at 02:22:59PM -0700, Carlos Sanchez wrote:
> Hi,
>
> Is it possible to create JIRA projects at the Codehaus for some of the
> sourceforge maven-plugins? The SF issue tracker is really a PITA.
Sounds like a good idea, but you'll have to ask the Codehaus des
Hi,
Is it possible to create JIRA projects at the Codehaus for some of the
sourceforge maven-plugins? The SF issue tracker is really a PITA.
Other suggestions are welcome.
Regards.
Carlos Sanchez
-
To unsubscribe, e-mail
On Mon, 2003-12-01 at 02:02, Vincent Massol wrote:
> Jason,
>
> I've checked one only but it seems they're not in the Maven category.
Hokay, I will add all the projects that I've created to the Maven
category.
The only plugin left to deal with now is the xdoc plugin now. It's the
only component
Hi Jason,
I've seen that you haven't modified the changes.xml from the different
maven plugin projects. It'll now be very very hard to find the new issue
numbers... and it's a pity to loose the issue information.
Thanks
-Vincent
--
Jason,
I've checked one only but it seems they're not in the Maven category.
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
entries?
Not necessarily. I think in a lot of cases the RM is not the lead.
> Thanks
> -Vincent
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: 20 November 2003 04:18
> > To: Maven Developers List
> >
MAIL PROTECTED]
> Sent: 20 November 2003 04:18
> To: Maven Developers List
> Subject: RE: [Status] Creation of new JIRA projects for Maven plugins
+ ot
> her stuff
>
> Why don't we just put the 'owner' as the of a in
> project.xml?
>
> This means we don't
,dion,...|CVSROOT
>
> Looks like you're rootish :)
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 20 November 2003 2:18 PM
> > To: Maven Developers List
> > Subject: RE: [Status] Creati
e do? Or is it
Release
> Manager, Lead, ...?
>
> - Brett
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 20 November 2003 2:18 PM
> > To: Maven Developers List
> > Subject: RE: [Status] Creation of n
[Status] Creation of new JIRA projects for Maven
> plugins + ot her stuff
>
>
> Why don't we just put the 'owner' as the of a in
> project.xml?
>
> This means we don't need to keep the wiki up to date separate
> from the
> project too, and it
n Developers List
> Subject: RE: [Status] Creation of new JIRA projects for Maven
> plugins + ot her stuff
>
>
> I believe Jason is the only one with commit rights to CVSROOT/avail.
>
> Jason, could you please bring the two into synch?
> --
> dIon Gillard, Multitask Consu
and maven.
> Would someone with necessary privs care to update it?
>
> Cheers,
> Brett
>
> > -Original Message-
> > From: Brett Porter
> > Sent: Monday, 17 November 2003 8:25 AM
> > To: 'Maven Developers List'
> > Subject: RE: [Statu
Why don't we just put the 'owner' as the of a in
project.xml?
This means we don't need to keep the wiki up to date separate from the
project too, and it comes out as part of the site generation.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Brett Po
.
Would someone with necessary privs care to update it?
Cheers,
Brett
> -Original Message-
> From: Brett Porter
> Sent: Monday, 17 November 2003 8:25 AM
> To: 'Maven Developers List'
> Subject: RE: [Status] Creation of new JIRA projects for Maven
> plugins + ot
> Who wants to take ownership for the other plugins? We should
> probably update the wiki page listing these ownerships.
>
I'll take idea, scm and cruisecontrol for now.
- Brett
Hi,
1/ I've started creating JIRA projects for maven plugins. I've done:
- maven-ant-plugin
- maven-checkstyle-plugin
- maven-clover-plugin
- maven-changes-plugin
- maven-changelog-plugin
2/ I've tried to move all existing issues to the new JIRA projects as
best as I could.
3
72 matches
Mail list logo
