I can see from MSHARED which uses the Maven Permissions Scheme that PMC
members have the ability to move issues. I'd be happy changing that to
allow committers to do the same, but I cannot find where I can edit the
scheme...
Guillaume
Lately I've found an occasional need to move a Jira issue between
projects; e.g. from maven-dependency-analyzer to
maven-dependency-plugin or vice versa. I think this requires the Jira
administrator to grant some sort of move issue permission. Is there
somebody here who can do that? It seems a reas
Hi,
Dependabot is a very useful tool as we know.
Most of (probably all) Maven / ASF projects have dedicated jira projects to
track changes.
When we create PR with jira issue reference in the PR title then "ASF
GitHub Bot" links PR with jira issue.
Maybe it will be useful (posible) when Dependa
n 11 Set 2020, 10:38 Bindul Bhowmik ha
> > scritto:
> >
> > > Hi,
> > >
> > > If I may chime in, the Maven (and most Apache) JIRA issues don't
> > > require a login to view. I believe the issue is that Amelia added a
> > > filter to the URL
:45, Enrico Olivelli wrote:
> I agree with Bindul
>
> I have never seen such blocks
>
> Enrico
>
> Il Ven 11 Set 2020, 10:38 Bindul Bhowmik ha
> scritto:
>
> > Hi,
> >
> > If I may chime in, the Maven (and most Apache) JIRA issues don't
> > requi
Clear, it is not an issue, just a matter of using the correct URL.
Robert
On 11-9-2020 11:18:45, Enrico Olivelli wrote:
I agree with Bindul
I have never seen such blocks
Enrico
Il Ven 11 Set 2020, 10:38 Bindul Bhowmik ha
scritto:
> Hi,
>
> If I may chime in, the Maven (and most Apa
I agree with Bindul
I have never seen such blocks
Enrico
Il Ven 11 Set 2020, 10:38 Bindul Bhowmik ha
scritto:
> Hi,
>
> If I may chime in, the Maven (and most Apache) JIRA issues don't
> require a login to view. I believe the issue is that Amelia added a
> filter to t
Hi,
If I may chime in, the Maven (and most Apache) JIRA issues don't
require a login to view. I believe the issue is that Amelia added a
filter to the URL pasted in the tweet, and the filter requires a
login.
So: https://issues.apache.org/jira/browse/MNG-6928 is viewable without
a login
Agreed. If there's anything that is too deliberate to discuss in the
open, there's the mailing list, direct email or what not.
Maarten
On 11/09/2020 09:51, Robert Scholte wrote:
Based on the https://twitter.com/ameliaeiras/status/1303815661307613184 and the
responses of Marten Deinum I agree
Based on the https://twitter.com/ameliaeiras/status/1303815661307613184 and the
responses of Marten Deinum I agree that it makes sense to make issues viewable
for all.
If there is no strong reason to keep it as it is, I'll ask our Jira
administrator if our scheme can be updated.
(looks like the
ld have JIRA tickets.
My opinion is clearly, yes. There must be a ticket for dep upgrades. You
have seen recently where a patch update of a Plexus Component has caused
a regression and you have spent time to track it down. Such changes
should be user visible.
The reason my I prefer JIRA issues for
yes. There must be a ticket for dep upgrades. You
have seen recently where a patch update of a Plexus Component has caused
a regression and you have spent time to track it down. Such changes
should be user visible.
The reason my I prefer JIRA issues for almost everything is that I don't
wan
Does the community have an consensus on whether to file JIRA tickets
for minor dependency upgrades that don't require large code changes?
I've been getting conflicting advice about this in code reviews.
Here's what our docs currently say, but you'll notice that dependency
upgrades fall somewhere i
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/107
You'll need to merge the resolver bugfixes as well to make the IT work, of
course.
[MRESOLVER-8](https://github.com/ChristianSchulte/maven-resolver/commit/2813a8f9e290f8a6523486c0ca
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/107
Fixes to various JIRA issues.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/maven master
Alternatively you can
I just looked at the issues with a fix version of 3.5.0-candidate.
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.5.0-candidate>
If not already done, I'd like to second the following issues:
MNG-5837 Syntax error in bin/mvn on Solaris SPA
ers, sorry
No Problem..
Thanks for cleaning up the thing.
Kind regards
Karl Heinz Marbaise
Regards,
Hervé
Le samedi 15 août 2015 10:37:40 Karl Heinz Marbaise a écrit :
Hi,
can someone explain why all these JIRA issues are flooding the dev list ?
Is this intentional ?
Kind regards
Karl
7:40 Karl Heinz Marbaise a écrit :
> Hi,
>
> can someone explain why all these JIRA issues are flooding the dev list ?
>
> Is this intentional ?
>
> Kind regards
> Karl Heinz Marbaise
>
> ---
Hi,
can someone explain why all these JIRA issues are flooding the dev list ?
Is this intentional ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail
gt; Hervé
> > - Mail d'origine -
> > De: Chris Graham
> > À: Maven Developers List
> > Envoyé: Wed, 22 Apr 2015 13:41:21 +0200 (CEST)
> > Objet: ASF Jira Issues
> >
> > Hi All.
> >
> > I can see that I'm a member of jira-use
t; Hervé
> - Mail d'origine -
> De: Chris Graham
> À: Maven Developers List
> Envoyé: Wed, 22 Apr 2015 13:41:21 +0200 (CEST)
> Objet: ASF Jira Issues
>
> Hi All.
>
> I can see that I'm a member of jira-users and maven-developers in the ASF
> jira.
>
t;
> Hervé
> - Mail d'origine -
> De: Chris Graham
> À: Maven Developers List
> Envoyé: Wed, 22 Apr 2015 13:41:21 +0200 (CEST)
> Objet: ASF Jira Issues
>
> Hi All.
>
> I can see that I'm a member of jira-users and maven-developers in the ASF
> jira.
>
&
41:21 +0200 (CEST)
Objet: ASF Jira Issues
Hi All.
I can see that I'm a member of jira-users and maven-developers in the ASF
jira.
I'd like to assign some work to myself, but I do not seem to be able too.
How does one d
Hi All.
I can see that I'm a member of jira-users and maven-developers in the ASF
jira.
I'd like to assign some work to myself, but I do not seem to be able too.
How does one do that?
-Chris
Den 4 feb 2015 04:00 skrev "Hervé BOUTEMY" :
>
> Le lundi 2 février 2015 10:23:00 Michael Osipov a écrit :
> > Hi folks,
> >
> > I have performed another cleanup on JIRA in the last couple of days,
most of
> > on old issues. Right now, we have more than 2000 open issues. Not
manageble
> > from my p
Le lundi 2 février 2015 10:23:00 Michael Osipov a écrit :
> Hi folks,
>
> I have performed another cleanup on JIRA in the last couple of days, most of
> on old issues. Right now, we have more than 2000 open issues. Not manageble
> from my point of view.
>
> I have noticed that several plugins hav
notice that I completely understand Andreas explanations about memory
requirements of m2e vs m-eclipse-p
but
> > The developer experience within eclipse is so much better after using the
> > maven-eclipse-plugin.
this one is more obscure to me
this doesn't change the fact that I like Andreas pl
Le lundi 2 février 2015 19:49:02 Andreas Gudian a écrit :
> I'm pretty sure I might be bashed for writing this, but what the heck... ;-)
>
> I do still see some need for the maven-eclipse-plugin.
>
> To be perfectly clear, I agree that m2e is by far superior in many ways,
> not only tech-wise, bu
On Monday, February 2, 2015, Olivier Lamy wrote:
> -1 for both archetype and stage plugin.
> Maybe I will have a look to fix issues if enough spare time..
> I don't understand such rush... AFAIK we are not a company with some budget
> and who need to justify a ratio between number of bugs and tim
-1 for both archetype and stage plugin.
Maybe I will have a look to fix issues if enough spare time..
I don't understand such rush... AFAIK we are not a company with some budget
and who need to justify a ratio between number of bugs and time spent on
projects.
On 2 February 2015 at 20:23, Michael
Great, Daniel, I thought I'm the only one thinking that way... ;-)
2015-02-02 19:38 GMT+01:00 Daniel Kulp :
>
> I’m -1 to retiring the maven-eclipse-plugin until the m2e stuff is at a
> state where it can be as flexible and useful as the maven-eclipse-plugin.
> Trying to bring a large complex pr
I'm pretty sure I might be bashed for writing this, but what the heck... ;-)
I do still see some need for the maven-eclipse-plugin.
To be perfectly clear, I agree that m2e is by far superior in many ways,
not only tech-wise, but also conceptionally.
Still, at work we had to migrate from m2e to m
I’m -1 to retiring the maven-eclipse-plugin until the m2e stuff is at a state
where it can be as flexible and useful as the maven-eclipse-plugin. Trying to
bring a large complex project like CXF into eclipse with m2e is PAINFUL and
doesn’t even result in fully configured and ready workspace.
Just to be perfectly clear:
I am volunteering to include archetype in the herd.
I have submitted INFRA-9100 to move it to git.
I have assigned http://jira.codehaus.org/browse/ARCHETYPE-471 to myself.
So no need to send any email announcing its demise.
---
Hi,
the plan was to release from almost all the plugins to make a last
releases which has Maven 2.2.1 minimum and JDK 5 min.
Furthermore I'm working on several of those plugins:
maven-docck-plugin,
maven-doap-plugin
maven-repository-plugin
maven-stage-plugin
maven-pdf-plugin
maven-archetype-p
People are making new archetypes every day.
I did a round of bugfixing a couple of years ago, I could do one again.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache
Agree with Anders:
* +1 to deprecate maven-eclipse-plugin (coming from an happy M2E user from
years), the community must acknowledge that this plugin is not the way to
go and there's a modern an well-maintained alternative.
* -1 to deprecate maven-archetype-plugin IMO it's still one of those
plugi
I strongly second that the maven-eclipse-plugin be retired. For us working
in Eclipse, the m2e integration is the way to go. Also, there has not been
any active work on that plugin for many years and I think we should clearly
indicate to the community that there is very little hope anyone would fix
Hi folks,
I have performed another cleanup on JIRA in the last couple of days, most of on
old issues.
Right now, we have more than 2000 open issues. Not manageble from my point of
view.
I have noticed that several plugins haven't been touched in years. What is the
status of
the following plugi
.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 8:04 PM
To: Maven Developers List
Subject: Re: Where to create JIRA issues for Maven documentation?
> But whatever I don't care as long as it's easy and _obvious_.
Adding a descriptio
But whatever I don't care as long as it's easy and _obvious_.
Adding a description to the JIRA project MNG, that provides a hyperlink to
MNGSITE and some hinting words might further help to direct users to the
right place.
It took me over a minute to find the right project (and I knew that it
f other random stuff on the default dashboard.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 7:35 PM
To: Maven Developers List
Subject: Re: Where to create JIRA issues for Maven documentation?
Yah, I actually agree with Dennis. I prefer them separate so I
a bunch of other random stuff on the default dashboard.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2008 7:35 PM
To: Maven Developers List
Subject: Re: Where to create JIRA issues for Maven documentation?
Yah, I actually agree with Dennis. I
to find if it's a component of MNG
rather than separate. So I would suggest we move MNGSITE over to MNG.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent:
Monday, March 24, 2008 11:39 AM
To: Maven Developers List
Subject: Where to create JIRA issues for Mave
onday, March 24, 2008 11:39 AM
To: Maven Developers List
Subject: Where to create JIRA issues for Maven documentation?
Hi,
It seems there are currently two places in JIRA to fill in issues
regarding
documentation:
- the components "Documentation: *" in project MNG and
- the project M
ect: Where to create JIRA issues for Maven documentation?
Hi,
It seems there are currently two places in JIRA to fill in issues
regarding
documentation:
- the components "Documentation: *" in project MNG and
- the project MNGSITE
Is this situation by design, i.e. are the projects/com
Hi,
It seems there are currently two places in JIRA to fill in issues regarding
documentation:
- the components "Documentation: *" in project MNG and
- the project MNGSITE
Is this situation by design, i.e. are the projects/components intended for
different purposes/audiences, or could we move
Done.
A lot of what I have in there is site and documentation, which
hopefully can be corralled in the near future.
Also, I have a lot of stuff surrounding maven-artifact - I hope when
we discuss the design of that that we can tie in the existing issues.
- Brett
On 05/06/2007, at 2:49 PM
Hi,
Can devs take a peek at issues they've raise and nuke/close any of
them they know to be fixed. I keep seeing large numbers of duplicates
and people probably remember their own issues. I think we could
probably get rid of a 15% of the issues just by devs going through
their own issues.
On 3/18/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > Actually I believe we should simply configure jira to not allow an issue
> > to
> > be closed without an assignee. The same should apply for not specifying a
> > "fix for" field, etc. Those fields should be defined as mandatory.
> -Original Message-
> From: Lukas Theussl [mailto:[EMAIL PROTECTED]
> Sent: dimanche 19 mars 2006 18:46
> To: Maven Developers List
> Subject: Re: Jira - Issues closed without assignee
>
> I think you misunderstood my point. It was not at all about opening
> iss
and I don't want to deter anybody else from taking a look at it).
-Lukas
Vincent Massol wrote:
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: dimanche 19 mars 2006 02:38
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
[snip]
> -Original Message-
> From: Lukas Theussl [mailto:[EMAIL PROTECTED]
> Sent: dimanche 19 mars 2006 02:38
> To: Maven Developers List
> Subject: Re: Jira - Issues closed without assignee
[snip]
> I also don't like the idea of making it obligatory to assign an
Honestly, apart from statistical purposes, I don't see the point in
having closed issues assigned to somebody at all. Would all the people
who have moved on to m2 take up an old m1 issue if it gets reopened
today? What about people who have left the project? IMO it's the project
lead/maintai
I agree. I don't want that we update all closed issues up until now, but
only that we take care to define the assignee from now.
Arnaud
On 3/18/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> As far as I'm concerned, setting the assignee to yourself when you close
> it has been accepted practice
As far as I'm concerned, setting the assignee to yourself when you close
it has been accepted practice for some time (but we don't need to go
back and change all the old ones).
That way, if it is reopened, the person that closed it can deal with it.
- Brett
Arnaud HERITIER wrote:
> Hi guys,
>
>
>
>
> Actually I believe we should simply configure jira to not allow an issue
> to
> be closed without an assignee. The same should apply for not specifying a
> "fix for" field, etc. Those fields should be defined as mandatory. Not
> sure
> how to do this with jira but I supposed it's possible.
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:50
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto
> -Original Message-
> From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
> Sent: samedi 18 mars 2006 17:50
> To: Maven Developers List
> Subject: Re: Jira - Issues closed without assignee
>
> Vincent Massol wrote:
> >
> >> -Original Message
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:31
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects
> -Original Message-
> From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
> Sent: samedi 18 mars 2006 17:31
> To: Maven Developers List
> Subject: Re: Jira - Issues closed without assignee
>
> Arnaud HERITIER wrote:
> > Hi guys,
> >
> > I
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects (particularly in m1) a lot of
issues closed (2033) but without assignee (698).
I think that it is a good practice to assign the issue to the one who
closed it (even if it's a Won't fix or duplicated status).
It's easi
Hi guys,
I noticed that we have in maven projects (particularly in m1) a lot of
issues closed (2033) but without assignee (698).
I think that it is a good practice to assign the issue to the one who
closed it (even if it's a Won't fix or duplicated status).
It's easier to see who closed it (
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mercredi 1 février 2006 23:04
> To: Maven Developers List
> Subject: Re: editing closed JIRA issues
>
> Brett Porter wrote:
> > It's not possible to replace the existing Mave
06 20:57
To: Maven Developers List
Subject: editing closed JIRA issues
I found this:
http://confluence.atlassian.com/pages/viewpage.action?pageId=121422
Vincent, could you help us set this up in our workflow?
I've created a new workflow called "Maven New" which allows edits even if
It's not possible to replace the existing Maven workflow?
Vincent Massol wrote:
>> -Original Message-
>> From: Brett Porter [mailto:[EMAIL PROTECTED]
>> Sent: mercredi 1 février 2006 20:57
>> To: Maven Developers List
>> Subject: editing closed JIRA
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 1 février 2006 20:57
> To: Maven Developers List
> Subject: editing closed JIRA issues
>
> I found this:
> http://confluence.atlassian.com/pages/viewpage.action?pageId=121422
>
I found this:
http://confluence.atlassian.com/pages/viewpage.action?pageId=121422
Vincent, could you help us set this up in our workflow?
Thanks,
Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[ http://jira.codehaus.org/browse/MPJIRA-17?page=all ]
Lukas Theussl closed MPJIRA-17:
---
Resolution: Fixed
> Plugin uses deprecated API to retrieve JIRA issues
> --
>
> Ke
[ http://jira.codehaus.org/browse/MPJIRA-17?page=all ]
Lukas Theussl updated MPJIRA-17:
Assign To: Lukas Theussl
Fix Version: 1.3
> Plugin uses deprecated API to retrieve JIRA iss
ve been deprecated in JIRA 3.3
(http://confluence.atlassian.com/display/JIRA/Parameter+changes+in+Issue+Navigator).
I will look into it.
> Plugin uses deprecated API to retrieve JIRA issues
> --
>
> Key: MPJIRA-17
> U
Plugin uses deprecated API to retrieve JIRA issues
--
Key: MPJIRA-17
URL: http://jira.codehaus.org/browse/MPJIRA-17
Project: maven-jira-plugin
Type: Bug
Versions: 1.2
Environment: JIRA 3.4.1-#107
e-
> > De : bob mcwhirter [mailto:[EMAIL PROTECTED]
> > Envoyé : mardi 20 juillet 2004 20:28
> > À : Maven Developers List
> > Objet : RE: JIRA issues pertaining to versions
> >
> > On Tue, 20 Jul 2004, Carlos Sanchez wrote:
> >
> > > What
+1 from me
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: mardi 20 juillet 2004 20:42
> To: 'Maven Developers List'
> Subject: RE: JIRA issues pertaining to versions
>
> I think (if others are agree) that it could be a good
--
> > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, July 20, 2004 5:51 PM
> > > To: Maven Developers List
> > > Subject: JIRA issues pertaining to versions
> > >
> > > Hi,
> > >
> > > I'm not sur
It should be changed for maven-plugins or it will be a nightmare with so
many plugins.
> -Original Message-
> From: bob mcwhirter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 20, 2004 8:28 PM
> To: Maven Developers List
> Subject: RE: JIRA issues pertaining to versi
n Developers List
> Objet : RE: JIRA issues pertaining to versions
>
> On Tue, 20 Jul 2004, Carlos Sanchez wrote:
>
> > What JIRA role is needed to add versions to plugins?
>
> Well, whatever role is specified by the project.
>
> I think Maven requires jira-adm
You must be administrator :-(
> -Message d'origine-
> De : Carlos Sanchez [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 20 juillet 2004 20:24
> À : 'Maven Developers List'
> Objet : RE: JIRA issues pertaining to versions
>
> What JIRA role
On Tue, 20 Jul 2004, Carlos Sanchez wrote:
> What JIRA role is needed to add versions to plugins?
Well, whatever role is specified by the project.
I think Maven requires jira-administrator, but that can certainly
be changed.
It could become maven-developers, or we could create yet-another
group
What JIRA role is needed to add versions to plugins?
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 20, 2004 8:15 PM
> To: 'Maven Developers List'
> Subject: RE: JIRA issues pertaining to versions
>
> +1 fo
0 juillet 2004 17:51
> À : Maven Developers List
> Objet : JIRA issues pertaining to versions
>
> Hi,
>
> I'm not sure what the standard practice is for queuing up issues to be
> resolved for a version but I think what we have going on is not quite
> optimal.
>
> When
ation of the issues. I'll do a little spring cleaning while I
move the issues.
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, July 20, 2004 5:51 PM
> > To: Maven Developers List
> > Subject: JIRA issues perta
elopers List
> Subject: JIRA issues pertaining to versions
>
> Hi,
>
> I'm not sure what the standard practice is for queuing up
> issues to be resolved for a version but I think what we have
> going on is not quite optimal.
>
> When planning a release I would like to
+1. I'd like it if the notification was turned off while this is suffeled
around, I don't want 100 jira mails popping up at the same time, too much
clutter.
--
Trygve
On Tue, Jul 20, 2004 at 11:50:59AM -0400, Jason van Zyl wrote:
> Hi,
>
> I'm not sure what the standard practice is for queuing
Sounds good to me.
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mardi 20 juillet 2004 17:51
> To: Maven Developers List
> Subject: JIRA issues pertaining to versions
>
> Hi,
>
> I'm not sure what the standard prac
Hi,
I'm not sure what the standard practice is for queuing up issues to be
resolved for a version but I think what we have going on is not quite
optimal.
When planning a release I would like to pick the issues that can be
tackled for a release and roadmapped. We have 120 issues outstanding for
1.
use that as a guide but I'm going to flush all plugin issues to a
respective plugin project so a clear view of what remains in the core
can easily be seen.
> Thanks
> -Vincent
>
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent
be good to get help from
all jira admins working on maven... :-) I'll also slowly continue to do
the job but help is most welcome.
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 29 November 2003 01:41
> To: Maven Developers
Vincent,
Is there an easy way to transfer issues to another project? I'm going to
continue your work on creating separate projects and I want to start
transfering issues to their respective plugins. Is this the approach you
took? I'll just follow in your footsteps.
Have
--
jvz.
Jason van Zyl
89 matches
Mail list logo
