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
Understood.
2. I still didn't understand: will the Jira issue identifiers change
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
Understood.
2. I still didn't understand: will the Jira issue identifiers
change
. 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 MPLUGIN-288 in ASF
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 MPLUGIN-288 in ASF or is
there
a risk that it changes?
Assuming that the project keys do not clash
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
lot of accounts are shared between Maven Jira projects
Understood.
2. I still didn't
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 MPLUGIN-288 in ASF or
is
there
a risk that it changes
Jira projects
Understood.
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?
Assuming that the project keys do not clash with existing ones then
that should be ok. Though
. 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 MPLUGIN-288 in ASF or is there a risk
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
lot of accounts are shared between Maven Jira projects
Understood.
2. I still didn't
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 understand: will the Jira issue identifiers change or
not? Will Codehaus MPLUGIN-288 migrate to MPLUGIN-288 in ASF or is there
a risk
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?
Regards
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] http://jira.codehaus.org/browse/MPLUGIN
Le lundi 5 janvier 2015 16:18:12
infrastructure have
founded on the sheer number: dozens. Infrastructure didn't feel that
they could support that many project, and the Maven project felt that
it would be very difficult to combine all of the many per-maven-plugin
JIRA projects into a single project with many components.
Can you tell
: dozens. Infrastructure didn't feel that
they could support that many project, and the Maven project felt that
it would be very difficult to combine all of the many per-maven-plugin
JIRA projects into a single project with many components.
Can you tell me why it would be difficult? E.g. I am
to combine all of the many per-maven-plugin
JIRA projects into a single project with many components.
Can you tell me why it would be difficult? E.g. I am envisioning a
single maven project, an each plugin has a component instead of a
separate project.
we use such a schema for parent POMS at ASF
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 plugins are products of the Maven PMC, we don't have any
fine-grained access control for anything else, so I don't see why
.
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 plugins are products of the Maven PMC, we don't have any
fine-grained access control for anything else, so I
.
In the past, discussions on moving onto ASF infrastructure have
founded on the sheer number: dozens. Infrastructure didn't feel that
they could support that many project, and the Maven project felt that
it would be very difficult to combine all of the many per-maven-plugin
JIRA projects
project felt that
it would be very difficult to combine all of the many
per-maven-plugin
JIRA projects into a single project with many components.
Can you tell me why it would be difficult? E.g. I am envisioning a
single maven project, an each plugin has a component instead
.
In the past, discussions on moving onto ASF infrastructure have
founded on the sheer number: dozens. Infrastructure didn't feel that
they could support that many project, and the Maven project felt that
it would be very difficult to combine all of the many per-maven-plugin
JIRA projects
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 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 despots.
There might be a
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 role of a developer in
project.xml?
This means we don't need to keep the wiki up to date separate from the
project too
is not the lead.
Thanks
-Vincent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL 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
Why don't we just put the 'owner' as the role of a developer 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:
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 her stuff
Who wants to take ownership for the other
projects for Maven
plugins + ot her stuff
Why don't we just put the 'owner' as the role of a developer 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
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] Creation of new JIRA projects for Maven
plugins + ot her stuff
I believe Jason
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
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 her stuff
Who wants to take ownership
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/ I've assigned
31 matches
Mail list logo
