file). Will update it later!
Matthias
Am 07.06.2025 um 10:04 schrieb Xeno Amess:
Thanks, glad to see github issues open.
Still have some questions about the current workflow.
Would you please update the CONTRIBUTING.md also? because I'm not
sure if a
jira ticket is still needed if we
some questions about the current workflow.
Would you please update the CONTRIBUTING.md also? because I'm not sure if a
jira ticket is still needed if we wanna some feature/bug fix
(as the current CONTRIBUTING.md of branch master still say we shall have
jira account & fill the jira ticket so I
Hi,
Thanks for the hard work.
I was thinking about something we could do to help/notify users who
took the time to create issues, such as informing them by adding a
link to the GH issue in the Jira issue as a comment.
Besides that, users will have no information on where to follow up
with their
Thanks, glad to see github issues open.
Still have some questions about the current workflow.
Would you please update the CONTRIBUTING.md also? because I'm not sure if a
jira ticket is still needed if we wanna some feature/bug fix
(as the current CONTRIBUTING.md of branch master still say we
Thx a lot for the hard work Matthias !
Le ven. 6 juin 2025 à 17:22, Matthias Bünger a écrit :
> Greetings everyone,
> I want to give you all a status information about our progress to
> migrate issues from JIRA to Github issues.
>
> As a reminder and for those who are not aware:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Infrastructure
Le vendredi 6 juin 2025, 17:22:20 CEST Matthias Bünger a écrit :
> Greetings everyone,
> I want to give you all a status information about our progress to
> migrate issues from JIRA to Github issues.
>
> As a reminder and f
Greetings everyone,
I want to give you all a status information about our progress to
migrate issues from JIRA to Github issues.
As a reminder and for those who are not aware:
Last december we decided to migrate to Github Issues. Three of the
reasons for this were
* issues and source code
:
>
>> I'm ready to submit some issues + patches and having weird problems with
>> the self-submit process. I have an existing JIRA account, and I've
>> definitely contributed to an Apache project in the past (read-only access
>> to ancient unix backups).
>>
I'll let Apache infra know!
Ben
On Sun, 30 Mar 2025, 18:07 Bear Giles, wrote:
> I'm ready to submit some issues + patches and having weird problems with
> the self-submit process. I have an existing JIRA account, and I've
> definitely contributed to an Apache projec
I'm ready to submit some issues + patches and having weird problems with
the self-submit process. I have an existing JIRA account, and I've
definitely contributed to an Apache project in the past (read-only access
to ancient unix backups).
When I try to log in it fails but when I tr
SD?
>
> changes-validate - goal uses schemas from current classloader ... it
> is copied into plugin jar during build.
>
>
> https://github.com/apache/maven-changes-plugin/blob/master/src/main/java/org/apache/maven/plugins/changes/schema/DefaultChangesSchemaValidator.java#L93
>
>
che/maven/plugins/changes/schema/DefaultChangesSchemaValidator.java#L93
>
> I can see all the JIRA releases now. Maybe I wasn't logged to JIRA. Odd &
> TY again for the quick response!
>
> Gary
>
> On Fri, Jan 3, 2025 at 10:32 AM Slawomir Jaranowski
> wrote:
>
>
D?
I can see all the JIRA releases now. Maybe I wasn't logged to JIRA. Odd &
TY again for the quick response!
Gary
On Fri, Jan 3, 2025 at 10:32 AM Slawomir Jaranowski
wrote:
> On Fri, 3 Jan 2025 at 16:01, Gary Gregory wrote:
> >
> > Hi All:
> >
> > I'
On Fri, 3 Jan 2025 at 16:01, Gary Gregory wrote:
>
> Hi All:
>
> I'm trying to debug an issue in MCHANGES M2 and that version not in Jira! I
> want to look at the ticket about making the "dev" attribute optional in M2
> (it's not optional BTW, it should be).
Hi All:
I'm trying to debug an issue in MCHANGES M2 and that version not in Jira! I
want to look at the ticket about making the "dev" attribute optional in M2
(it's not optional BTW, it should be).
There must be a missing unit test because the XSD still requires "dev&qu
me of the variants and -1
on others.
PMC quorum: reached
So we can officially start switching issues from JIRA to GitHub -
project by project.
--
Sławomir Jaranowski
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.or
+1
Am Mi., 18. Dez. 2024 um 08:30 Uhr schrieb Slawomir Jaranowski
:
>
> Hi,
>
> I open vete for question:
>
> Do we want to Switch to GitHub issues from JIRA?
>
> Discussion was in thread:
> https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
>
>
+1
On Fri, 20 Dec 2024 at 10:22, Slawomir Jaranowski
wrote:
> +1
>
> On Wed, 18 Dec 2024 at 08:29, Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > I open vete for question:
> >
> > Do we want to Switch to GitHub issues from J
+1
On Wed, 18 Dec 2024 at 08:29, Slawomir Jaranowski
wrote:
>
> Hi,
>
> I open vete for question:
>
> Do we want to Switch to GitHub issues from JIRA?
>
> Discussion was in thread:
> https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
>
> Abou
+1 (non binding)
Am 18.12.24 um 08:29 schrieb Slawomir Jaranowski:
Hi,
I open vete for question:
Do we want to Switch to GitHub issues from JIRA?
Discussion was in thread:
https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
About technical questions how we will switch, if
open vete for question:
> >
> >Do we want to Switch to GitHub issues from JIRA?
> >
> > Discussion was in thread:
> > https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
> >
> > About technical questions how we will switch, if migration is needed
+1
This vote is not about _how_ so I guess it is fine to continue that
discussion in parallel ;-)
Brgds
Jesper Udby
On 18/12/2024 08.29, Slawomir Jaranowski wrote:
Hi,
I open vete for question:
Do we want to Switch to GitHub issues from JIRA?
Discussion was in thread:
https
+1
On Wed, Dec 18, 2024, 08:31 Slawomir Jaranowski
wrote:
> Hi,
>
> I open vete for question:
>
> Do we want to Switch to GitHub issues from JIRA?
>
> Discussion was in thread:
> https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
>
> About technica
+1
Am 18.12.2024 um 08:29 schrieb Slawomir Jaranowski:
Hi,
I open vete for question:
Do we want to Switch to GitHub issues from JIRA?
Discussion was in thread:
https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
About technical questions how we will switch, if migration is
This question is ill posed. There were multiple proposals for what
should and should not be migrated, whether old issues would remain in
Jira, etc. I'd vote +1 on some of the variants and -1 on others.
On Wed, Dec 18, 2024 at 7:31 AM Slawomir Jaranowski
wrote:
>
> Hi,
>
>
+1
śr., 18 gru 2024, 09:02 użytkownik Guillaume Nodet
napisał:
> +1
>
>
> Guillaume Nodet
>
>
>
> Le mer. 18 déc. 2024 à 08:31, Slawomir Jaranowski
> a écrit :
>
> > Hi,
> >
> > I open vete for question:
> >
+1
Guillaume Nodet
Le mer. 18 déc. 2024 à 08:31, Slawomir Jaranowski
a écrit :
> Hi,
>
> I open vete for question:
>
> Do we want to Switch to GitHub issues from JIRA?
>
> Discussion was in thread:
> https://lists.apache.org/thread/jskz22vs
Hi,
I open vete for question:
Do we want to Switch to GitHub issues from JIRA?
Discussion was in thread:
https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
About technical questions how we will switch, if migration is needed
we will discuss per repository such each repository
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 se
+1 from me
On Wed, 28 Aug 2024 at 20:24, Konrad Windszus wrote:
> Hi everyone,
> I consider the automatic JIRA comments being added for each GitHub PR
> comment quite verbose and redundant. Also the formatting is in some cases
> broken because it doesn’t properly escape for th
s to match the right messages, I might even change the rule to
just delete those.
So +1 on disabling this from my side.
Maarten
On 28/08/2024 20:23, Konrad Windszus wrote:
Hi everyone,
I consider the automatic JIRA comments being added for each GitHub PR comment quite
verbose and redundant.
Hi everyone,
I consider the automatic JIRA comments being added for each GitHub PR comment
quite verbose and redundant. Also the formatting is in some cases broken
because it doesn’t properly escape for the Confluence markdown used by JIRA
(e.g. look at
https://issues.apache.org/jira/browse
Hey all,
when I started to read through the Maven JIRA issues I noticed that
there are many without a description that people, who were not involved
in discussions / coding in where an issues raised from, can hardly
understand the issue and therefore also can't get their hands on or
contr
aybe it's only me
>
>
Yes, you are right.
To be honest I also like GH release notes, and I think that is more
readable.
It is also used by other tools like dependabot.
Moreover, I think that most users can not reach release notes in Jira - it
is visible for logged users.
But we s
t;
> > On Mon, Nov 7, 2022, 20:05 Olivier Lamy wrote:
> >
> >> On Tue, 8 Nov 2022 at 10:59, Gary Gregory
> wrote:
> >> >
> >> > FYI, and FWIW, Log4j is planning on switch from Jira to GitHub for
> >> issues,
> >> > and release
What countries are those BTW?
Gary
On Mon, Nov 7, 2022, 21:52 Gary Gregory wrote:
>
>
> On Mon, Nov 7, 2022, 20:05 Olivier Lamy wrote:
>
>> On Tue, 8 Nov 2022 at 10:59, Gary Gregory wrote:
>> >
>> > FYI, and FWIW, Log4j is planning on switch from Ji
On Mon, Nov 7, 2022, 20:05 Olivier Lamy wrote:
> On Tue, 8 Nov 2022 at 10:59, Gary Gregory wrote:
> >
> > FYI, and FWIW, Log4j is planning on switch from Jira to GitHub for
> issues,
> > and release notes: https://issues.apache.org/jira/browse/LOG4J2-3628
> >
>
On Tue, 8 Nov 2022 at 10:59, Gary Gregory wrote:
>
> FYI, and FWIW, Log4j is planning on switch from Jira to GitHub for issues,
> and release notes: https://issues.apache.org/jira/browse/LOG4J2-3628
>
So you mean using ONLY gh for issues?
So by doing this, you will exclude peop
FYI, and FWIW, Log4j is planning on switch from Jira to GitHub for issues,
and release notes: https://issues.apache.org/jira/browse/LOG4J2-3628
Gary
On Mon, Nov 7, 2022, 19:16 Olivier Lamy wrote:
> well I just see GH release note as a cherry on the cake.
> as long as the rest is done.
to have cherry on the top for users
Especially when the rest of our long procedure has been done.
On Tue, 8 Nov 2022 at 09:00, Slawomir Jaranowski wrote:
>
> Hi,
> I start a discussion ... as beginning - some my loose thoughts
>
> We use Jira (for most of) as our primary issues managem
Hi,
I start a discussion ... as beginning - some my loose thoughts
We use Jira (for most of) as our primary issues management system.
We manage release notes in Jira - it is the source for announcements.
In some projects we have GitHub releases notes.
In some cases we use release-drafter for
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 (pos
Hi all,
Now that CDI is gone we still have some leaking packages not in a (almost)
pure maven ecosystem:
https://github.com/apache/maven/blob/406c525ec45da466387dbf19f7fd8ed1d9885e66/maven-core/src/main/resources/META-INF/maven/extension.xml#L98
(pure kind of means plexus/maven/sonatype/aether ev
Hi all,
Last Thursday and Friday, I've received well over 400 notifications from
Apache JIRA, all by the "Hudson" user (now Jenkins). They notified me of
a failed job regarding a ticket I was watching. Not only does it annoy
me, it also annoys people who reported a ticket [1]
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
um 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 Maven projects are missing an explicit Issue Security scheme)
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
pzygielo commented on a change in pull request #3:
URL: https://github.com/apache/maven-project-utils/pull/3#discussion_r453213245
##
File path: pom.xml
##
@@ -46,7 +46,7 @@ under the License.
jira
-https://issues.apache.org/jira/browse/MSHARED/component
slachiewicz merged pull request #3:
URL: https://github.com/apache/maven-project-utils/pull/3
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
elharo opened a new pull request #3:
URL: https://github.com/apache/maven-project-utils/pull/3
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
I'm helping someone dust this off as a warm up to development in the
plugin. Could folks have a look at the JIRA and see if the feature makes
sense?
Hi,
On 27.04.20 17:10, Michael Osipov wrote:
Am 2020-04-27 um 16:20 schrieb Elliotte Rusty Harold:
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 th
Am 2020-04-27 um 16:20 schrieb Elliotte Rusty Harold:
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 doc
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
upg
e requests that were incomplete and hard
to follow. There were also many patches submitted by non-committers
that had never been reviewed. We might want to rethink how we accept
new feature and model change requests. Filing such a request in Jira
seems likely to lead to a frustrating experience f
>> One thing we should try going forward is be more ready to won't fix
>> and close bugs and RFEs we disagree with. I've seen several examples
>> where the comments indicate the maintainers did not agree with the
>> issue, but it still wasn't closed. E.g.
>>
t agree with the
> issue, but it still wasn't closed. E.g.
>
> https://issues.apache.org/jira/browse/SUREFIRE-1227
>
> Closing an issue is not irrevocable. Issues can always be reopened, if
> the reporter or anyone else disagrees. Indeed it is more respectful to
> report
h the bugs I found this interesting bit of history:
> >
> > https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
> >
> > It seems like we've been here before. Some of the bugs that were
> > autoclosed then were reopened and are now scheduled for a
One thing we should try going forward is be more ready to won't fix
and close bugs and RFEs we disagree with. I've seen several examples
where the comments indicate the maintainers did not agree with the
issue, but it still wasn't closed. E.g.
https://issues.apache.org/jira/brows
I will exlude those. It does not makes sense to close/reopen again.
Am 2019-12-20 um 12:29 schrieb Elliotte Rusty Harold:
While working through the bugs I found this interesting bit of history:
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like
While working through the bugs I found this interesting bit of history:
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like we've been here before. Some of the bugs that were
autoclosed then were reopened and are now scheduled for autoclose
again
Ah sorry...
now I'm not able to read...
everything fine...
Kind regards
Karl Heinz Marbaise
On 15.12.19 22:58, Karl Heinz Marbaise wrote:
Hi,
to be honest I'm confused as well?
Have we decided to do a another 3.6.X release? Did I miss something?
Kind regards
Karl Heinz Marbaise
On 15.12.19
Hi,
to be honest I'm confused as well?
Have we decided to do a another 3.6.X release? Did I miss something?
Kind regards
Karl Heinz Marbaise
On 15.12.19 12:07, Elliotte Rusty Harold wrote:
I notice I'm confused. Wasn't Maven 3.6.0-3.6.3 already released?
On Sat, Dec 14, 2019 at 2:28 PM Enrico
@Elliotte
I am so sorry
I meant to send that email to d...@zookeeper.apache.org
Gmail autopletion changed that address
I apologize for the inconvenience
Enrico
Il giorno dom 15 dic 2019 alle ore 12:08 Elliotte Rusty Harold <
elh...@ibiblio.org> ha scritto:
> I notice I'm confused. Wasn't Maven
I notice I'm confused. Wasn't Maven 3.6.0-3.6.3 already released?
On Sat, Dec 14, 2019 at 2:28 PM Enrico Olivelli wrote:
>
> HI,
> I have moved to fixversion=3.7.0 all of the issues with fixversion = 3.6.0
> and resolution = empty.
>
> Please add the '3.6.0' label to the issues that should go int
HI,
I have moved to fixversion=3.7.0 all of the issues with fixversion = 3.6.0
and resolution = empty.
Please add the '3.6.0' label to the issues that should go into 3.6.0.
Candidates are:
- blocker issues (regressions)
- build environment issues
- flaky tests
- patches that are really ready
Am 2019-12-13 um 16:08 schrieb Elliotte Rusty Harold:
NVM, I seem to have access now. I think I just needed to logout with
my old credentials and back in with the new ones.
Elliotte,
please go through the list and update those tickets you seen to be
addressible within a decent timeframe.
Mi
NVM, I seem to have access now. I think I just needed to logout with
my old credentials and back in with the new ones.
On Fri, Dec 13, 2019 at 9:56 AM Elliotte Rusty Harold
wrote:
>
> On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly
> wrote:
> > I think we have some crazy permissions that Brian
On Thu, Dec 12, 2019 at 6:56 PM Stephen Connolly
wrote:
> I think we have some crazy permissions that Brian manages. Ldap just fixes
> the account name to match across systems AIUI
>
That's probably true. As of an hour ago, I did not seem able to close issues.
--
Elliotte Rusty Harold
elh...@i
On Thu 12 Dec 2019 at 17:31, Robert Scholte wrote:
> IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do
> this anymore. All should be in place by now.
>
I think we have some crazy permissions that Brian manages. Ldap just fixes
the account name to match acros
IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do this
anymore. All should be in place by now.
thanks,
Robert
On 12-12-2019 15:20:24, Stephen Connolly
wrote:
On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold
wrote:
> On Mon, Dec 9, 2019 at 3:18 PM Michael Osip
urther. Right now, almost anyone can file a bug
> but few people can resolve and close them. I can't, for example, even
> when I see one that's clearly no longer relevant. :-(
As soon as Brian fixes your JIRA permissions you’ll be able too... your
committer status is only freshly m
On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
>
> Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > Please don't. There are certainly some real and important issues in
> > there. More importantly, users spent a great deal of effort and time
> > to file those. Bulk closing them tells
te:
Hi folks,
after at least one year of silence, I'd like to perform another JIRA
issue cleanup for issues which have been not touched for more than three
years.
Query:
https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20A
7:50 AM Michael Osipov wrote:
Hi folks,
after at least one year of silence, I'd like to perform another JIRA
issue cleanup for issues which have been not touched for more than three
years.
Query:
https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven
dy
> fixed, moot, or things we expressly chose not to do. However this
> should be decided case by case. We can't simply close our eyes and
> pretend they're all irrelevant.
>
> On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov wrote:
> >
> > Hi folks,
> >
ks,
>
> after at least one year of silence, I'd like to perform another JIRA
> issue cleanup for issues which have been not touched for more than three
> years.
>
> Query:
> https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20update
Am 2019-12-08 um 13:55 schrieb Maarten Mulders:
Hi Michael,
Great initiative. After logging in to JIRA, accessing your link shows
"The requested filter doesn't exist or is private."
This means I'm not able to verify whether there are issues in that list
that are val
Hi Michael,
Great initiative. After logging in to JIRA, accessing your link shows
"The requested filter doesn't exist or is private."
This means I'm not able to verify whether there are issues in that list
that are valid for me.
Is there another way to find those issues?
Hi folks,
after at least one year of silence, I'd like to perform another JIRA
issue cleanup for issues which have been not touched for more than three
years.
Query:
https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-1
lly I like details. And if there is one JIRA per upgrade,
it maps better to the git log because I don't think people are bumping
unrelated dependencies in the same commit, right?
However, my question is why version 4.2 was selected. 4.4 is out, is
there something broken in versions > 4.2
Yes Robert, thank you for the suggestions - more changes of this type will
be combined.
Sylwester
sob., 19 paź 2019 o 22:32 Robert Scholte napisał(a):
> Maybe it is me, be I don't think having a separate jira issue for every
> updated dependency adds value.
> It makes the
Maybe it is me, be I don't think having a separate jira issue for every
updated dependency adds value.
It makes the release notes unnecessary long (in a time where people
already are bad readers).
As a user I expect dependency updates to be part of every release.
1 Jira item would be
On 2019-08-22 04:39, wrote:
Works fine for me, are you logged in?
https://issues.apache.org/jira/projects/MNG/summary
- Eric L
when will the maven jira be ok?
it has been down for several days.
-
To unsubscribe, e
when will the maven jira be ok?
it has been down for several days.
Just fyi, am aware of 3+2 oss solutions out there (the +2 are the trimmed
ones)
On Sat, Jul 6, 2019, 00:26 dzikoysk (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/MNG-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168
Il ven 26 apr 2019, 08:50 Olivier Lamy ha scritto:
> version created
>
Thanks!
Enrico
>
> On Fri, 26 Apr 2019 at 03:12, Enrico Olivelli wrote:
>
> > Hi,
> > I am cutting release 2.22.2 for surefire.
> > Can any JIRA admin create the 2.22.2 version ?
> >
version created
On Fri, 26 Apr 2019 at 03:12, Enrico Olivelli wrote:
> Hi,
> I am cutting release 2.22.2 for surefire.
> Can any JIRA admin create the 2.22.2 version ?
>
> I am also sseing a 2.22.1 version, this is to be closed, isn't it ?
Hi,
I am cutting release 2.22.2 for surefire.
Can any JIRA admin create the 2.22.2 version ?
I am also sseing a 2.22.1 version, this is to be closed, isn't it ?
Thanks
Enrico
-
To unsubscribe, e-mail: dev-uns
nks,
> >> Robert
> >>
> >> On Sat, 05 Jan 2019 12:11:41 +0100, Enrico Olivelli <
> eolive...@gmail.com>
> >> wrote:
> >>
> >> > Can any admin create this project ?
> >> > for Maven Scripting Plugin
> >> > https:
13:27 Robert Scholte ha scritto:
>>
>> Brian,
>>
>> can you pick this up?
>>
>> thanks,
>> Robert
>>
>> On Sat, 05 Jan 2019 12:11:41 +0100, Enrico Olivelli
>> wrote:
>>
>> > Can any admin create this project ?
>> > fo
; - pom.xml
> > - via packaging-plugin
> > - parent (custom or new maven-defaults-plugins)
> > - super pom
> > - maven core
> >
> > thanks,
> > Robert
> >
> > On Mon, 14 Jan 2019 12:01:00 +0100, Hervé Boutemy (JIRA)
> >
Github user ofarganc closed the pull request at:
https://github.com/apache/maven-pom/pull/4
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user ofarganc opened a pull request:
https://github.com/apache/maven-pom/pull/4
[MPOM-209] correct jira component url.
The Jira URL with the component Id was not valid id so changed it to
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20component
ontrolled.
> > > These are probably all variants I can think of
> > > - pom.xml
> > > - via packaging-plugin
> > > - parent (custom or new maven-defaults-plugins)
> > > - super pom
> > > - maven core
> > >
> > > thanks,
>
1 - 100 of 30196 matches
Mail list logo
