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 should
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 swit
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 p
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.
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 management system.
> We
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
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
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].
A
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 pasted in
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
> > require a lo
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
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 https
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)
thanks,
Robert
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
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
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
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 this in code
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 docs currently say
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
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 for contributors and
revie
gt; 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://iss
e
> 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
> reporters to be politely h
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 autoclose
&
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/browse/SUREFIRE-1227
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. Any
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
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
@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
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.
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
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 across sys
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 Osipov wr
lmost 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 minted! (welcome/congrats)
Another issue
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
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=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved
:
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=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution
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,
> >
> > after at least
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=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20re
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 va
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?
Cheers
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=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND
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?
- Eric L
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 rele
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 good
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=16879546#comment
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-unsubscr
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
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)
> >
> > wrote:
> > > Hervé
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
probably all variants I can think of
> > > - pom.xml
> > > - via packaging-plugin
> > > - parent (custom or new maven-defaults-plugins)
> > > - super pom
> > > - maven core
> > >
> > > thanks,
> > > Robert
> > >
&
On Tue, 15 Jan 2019 17:04:27 +0100, Hervé BOUTEMY
wrote:
Currently, packaging plugins do nothing in general, since it's Maven
core that
does the job:
It was a long time ago that we started this. So I guess that we started
moving the configuration to the packaging-plugins, in order to
hese 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,
> > Robert
> >
> > On Mon, 14 Jan 2019 12:01:00 +0100, Herv
to document how plugins are controlled.
> 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,
> Robert
>
> On Mon, 14 Jan 2019 12:01:00 +0
- 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)
wrote:
Hervé Boutemy created MPOM-215:
--
Summary: Create a new parent POM to lock down plugins
Ping
Il dom 6 gen 2019, 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 ?
> > for Maven Scripting Plu
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 ?
for Maven Scripting Plugin
https://issues.apache.org/jira/browse/MSCRIPTING
Regards
Enrico
Can any admin create this project ?
for Maven Scripting Plugin
https://issues.apache.org/jira/browse/MSCRIPTING
Regards
Enrico
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
First merge, and first failed build ;-)
Jenkins - Run ITs Linux Java 8 :
remote file operation failed:
/home/jenkins/jenkins-slave/workspace/maven-box_maven_master-DVEN5KAF4FLE3WDK7SWFNYUY4YZ7X45JVWYY6FZT5ZEB3CLWABVQ/test
at hudson.remoting.Channel@f03fce5:H27: java.nio.file.FileSystemException:
Hi Sylwester,
as you wrote the IT's are fine and now you can merge that branch back to
master. Just to be sure check the master if something has came into
master ...and make a rebase against master...(I expect that you don't
get something).
If you get something new to the rebase and make a
little did.
Should we do this again? The list won't get shorter and a lot of them do
not even contain a sample project.
JIRA query:
https://issues.apache.org/jira/issues/?jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-156w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created
-closed issues, sometimes they are indeed interesting to add even
though the reporter didn't ask to reopen such issue.
thanks,
Robert
[1]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+JIRA+issues+overview
On Thu, 08 Mar 2018 11:16:57 +0100, Martijn Verburg
<martijnv
han three (3) years.
> >
> > The last two times I autoclosed them with a message. People could request
> > a reopen, very little did.
> >
> > Should we do this again? The list won't get shorter and a lot of them do
> > not even contain a sample project.
> >
>
ears.
>
> The last two times I autoclosed them with a message. People could request
> a reopen, very little did.
>
> Should we do this again? The list won't get shorter and a lot of them do
> not even contain a sample project.
>
> JIRA query: https://issues.apache.org/jira/i
won't get shorter and a lot of them do
not even contain a sample project.
JIRA query:
https://issues.apache.org/jira/issues/?jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-156w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC
Please comment!
Michael
on the jira
and then provide follow up.
One small matter of clarification, I was talking specifically about the JIRA
project role of contributor (or its equivalent if the Maven project uses some
bespoke set of jira project configurations). I'm not looking to apply the
patch, merely place
.
thanks,
Robert
[1] https://maven.apache.org/guides/development/guide-committer-school
On Fri, 02 Mar 2018 15:36:15 +0100, Sean Busbey <bus...@apache.org> wrote:
Hi!
Could someone give me contributor status in jira so I can assign
MJAVADOC-444 to myself and put it in patch available
Hi!
Could someone give me contributor status in jira so I can assign MJAVADOC-444
to myself and put it in patch available status?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
ersions can be deployed on the class
>> path with JDK 9.
>>
>> In time they will be deployable as modules too and this will allow them to
>> be deployed on the upgrade module path (--upgrade-module-path) to
>> upgrade/override the module in the run-time image with t
the transaction
> API as there are a couple of issues to sort out there before it can be
> deployed as a module.
>
> As I understand it, the Spring folks in the JIRA issue are deploying the
> JTA JAR file on the class path. That should just work but is complicated by
> `-
-time image with the standalone or
Java EE module. This will actually work with all except for the
transaction API as there are a couple of issues to sort out there before
it can be deployed as a module.
As I understand it, the Spring folks in the JIRA issue are deploying the
JTA JAR file
ava/jdk9/docs/api/java.base-summary.html)
Currently I have no solution as there is no official maven dependency for
java.sql package
Enrico
2017-09-29 9:35 GMT+02:00 Robert Scholte <rfscho...@apache.org>:
> Hi Tibor,
>
> moving this to the dev-list, I don't think JIRA
Hi Tibor,
moving this to the dev-list, I don't think JIRA is the right place for
this kind of discussions.
bq. This is not a regression and not a bug in Surefire.
Sorry, I don't agree with you. The Java8 project provided by Stéphane
works with 2.20.0, but not with 2.20.1, so for me
Hi,
based on my earlier request in INFRA ticket[1] a new schema is already
there cause there were things not the best for example having an entry
"Question" which often lead people to use JIRA as a user forum..which is
now no possible anymore...
From my point of view this schema
wrote:
Does it mean that we have to post new Vote on separate Maven Scheme?
On Fri, Sep 8, 2017 at 10:05 AM, Robert Scholte <rfscho...@apache.org>
wrote:
This is part of the scheme in Jira.
Since there's a proposal to make a separate Maven Scheme, this request
should be added as we
Does it mean that we have to post new Vote on separate Maven Scheme?
On Fri, Sep 8, 2017 at 10:05 AM, Robert Scholte <rfscho...@apache.org>
wrote:
> This is part of the scheme in Jira.
> Since there's a proposal to make a separate Maven Scheme, this request
> should be added as w
This is part of the scheme in Jira.
Since there's a proposal to make a separate Maven Scheme, this request
should be added as well.
Robert
On Fri, 08 Sep 2017 08:53:31 +0200, Anders Hammar <and...@hammar.net>
wrote:
I agree, it's for us as committers to decide.
/Anders
On Fri,
I agree, it's for us as committers to decide.
/Anders
On Fri, Sep 8, 2017 at 8:51 AM, Michael Osipov <micha...@apache.org> wrote:
> Am 2017-09-08 um 00:42 schrieb Tibor Digana:
>
>> I found out that users create an issue in Jira and *assign version* [1].
>> I remember th
Am 2017-09-08 um 00:42 schrieb Tibor Digana:
I found out that users create an issue in Jira and *assign version* [1].
I remember this did not happen in old Jira.
So I decide to report a ticket in INFRA.
Do you have the same experiences?
What's your opinion about it?
[1]: https
I found out that users create an issue in Jira and *assign version* [1].
I remember this did not happen in old Jira.
So I decide to report a ticket in INFRA.
Do you have the same experiences?
What's your opinion about it?
[1]: https://issues.apache.org/jira/browse/INFRA-15047
--
Cheers
Tibor
> subprojects as well.
>
> thanks,
> Robert
>
> ps Stephen gave me the +1 for merging.
>
>
> On Thu, 24 Aug 2017 14:30:00 +0200, Igor Fedorenko (JIRA)
> <j...@apache.org> wrote:
>
> >
> > [
> > https://issues.apache.or
on locally and run other Maven
subprojects as well.
thanks,
Robert
ps Stephen gave me the +1 for merging.
On Thu, 24 Aug 2017 14:30:00 +0200, Igor Fedorenko (JIRA)
<j...@apache.org> wrote:
[
https://issues.apache.org/jira/brow
ich 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) switch your other schemes to match MASSEMBLY - meaning in addition to
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:
rojects...
>
> 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 additi
1 - 100 of 28875 matches
Mail list logo
