+1
this time, I could reproduce the build, done with JDK 8 on Windows
Regards,
Hervé
Le vendredi 2 octobre 2020, 20:32:20 CEST Michael Osipov a écrit :
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628
> rsion=12348853
>
> There are
asfgit closed pull request #206:
URL: https://github.com/apache/maven-site/pull/206
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 to go to
elharo opened a new pull request #206:
URL: https://github.com/apache/maven-site/pull/206
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 to
Sadly, I fully agree with Robert :-(
Am 2020-10-04 um 16:11 schrieb Robert Scholte:
As you know, the truth right now it is impossible to keep up. The amount of
mails and PRs waiting for responses exceeds our capacity.
So it is a matter of prioritizing, and yes, that could mean that PRs will
Build is back to normal. Even the previous failure does not affect any
downstream users.
Do you still want to cast -1?
Am 2020-10-04 um 12:53 schrieb Elliotte Rusty Harold:
Maven-resolver has been failing at head for several days:
Am 2020-10-02 um 20:32 schrieb Michael Osipov:
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348853
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissues
Thanks for the mentioning the trick. I experimented a bit and it seems,
"invoker.toolchain.jdk.version" is indeed working as expected. It was
probably a temporary hickup on the jenkins build nodes.
However, toolchains.xml is only available on linux nodes, not on Windows
nodes. I've create a INFRA
elharo commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499269010
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -403,6 +403,56 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2
kwin commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499264802
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -403,6 +403,56 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2
My experience is that the better contributions come from people who need to
get work done, which is usually best exemplified through bug fix PRs.
If I were to manage incoming PRs for a hackathon event, I would not want to
do so without a solid set of Jiras for new features and bugs, otherwise
You are right that, but this is a tricky situation:
* We need more committers to accept more PRs.
* We need to accept more PRs to encourage contributors to contribute more often.
* Contributions need to contribute accepted PRs more often to become committer.
So the sole possible solutions are:
elharo commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499259831
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -403,6 +403,56 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2
kwin commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499259005
##
File path: content/apt/guides/mini/guide-multiple-repositories.apt
##
@@ -102,3 +104,15 @@ mvn -Pmyprofile ...
activate multiple profiles
kwin commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499258979
##
File path: content/apt/guides/mini/guide-multiple-repositories.apt
##
@@ -29,7 +29,7 @@
Setting up Multiple Repositories
There are two different
kwin commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499258960
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -403,6 +403,56 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2
Which is why I am doing the same sadly over at Apache Commons and forging
ahead with regular work. I considered proposing one repo but that would
only open the floodgates...
Gary
On Sun, Oct 4, 2020, 10:11 Robert Scholte wrote:
> As you know, the truth right now it is impossible to keep up.
As you know, the truth right now it is impossible to keep up. The amount of
mails and PRs waiting for responses exceeds our capacity.
So it is a matter of prioritizing, and yes, that could mean that PRs will stay
unanswered.
IF we would also join hacktober, we must change those priorities for a
First working version is ready:
https://github.com/apache/maven-studies/pull/2
I'm waiting for your opinion
pt., 2 paź 2020 o 17:05 Slawomir Jaranowski
napisał(a):
> Targeting to maven 3.7.0-SNAPSHOT makes easier access to Transformer api.
> So one issue is need to resolve:
>
Same for me - I think having (new) contributions is important, so I will
reserve some time for that in this month.
From the contributor point of view, a PR counts if:
Submitted in a repo with the hacktoberfest topic AND
during the month of October AND (
The PR is merged OR
The PR is
Robert,
in fact I think it would be an even better signal to new contributors is at
least 5 committers would agree to pick up PRs for a whole year.
-Markus
-Ursprüngliche Nachricht-
Von: Robert Scholte [mailto:rfscho...@apache.org]
Gesendet: Sonntag, 4. Oktober 2020 10:55
An: Maarten
I'll look at some, but I can't promise highest priority.
On Sun, Oct 4, 2020 at 4:55 AM Robert Scholte wrote:
>
> I think the hacktober is a good initiative.
> Just be aware that we need to respond to these PRs ASAP, otherwise it might
> work against us.
> We already have a huge amount of PRs
elharo commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499234532
##
File path: content/apt/guides/introduction/introduction-to-profiles.apt
##
@@ -403,6 +403,56 @@ mvn groupId:artifactId:goal -P !profile-1,!profile-2
The failure is in the release candidate. It appears to be a result of
https://issues.apache.org/jira/browse/MRESOLVER-136 which requires
Java 8 to build and thus also fails on JDK 7 (though the build also
fails on JDK 11, perhaps for other reasons.)
My initial thought is that we should roll this
Maven-resolver has been failing at head for several days:
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/26/
Not sure if the offending PR is included in the release candidate but
either way I'd prefer not to release in an unstable state in case an
emergency
kwin commented on a change in pull request #205:
URL: https://github.com/apache/maven-site/pull/205#discussion_r499223023
##
File path: content/apt/guides/mini/guide-multiple-repositories.apt
##
@@ -52,11 +52,15 @@ Setting up Multiple Repositories
++
+You can give
I think the hacktober is a good initiative.
Just be aware that we need to respond to these PRs ASAP, otherwise it might
work against us.
We already have a huge amount of PRs that still need to be reviewed, so it is
not like we don't have enough PRs.
I think we need at least 5 committers that
+1 Non-binding. Seems to be working fine on my custom artefact resolving
plugin/library.
On 3 October 2020 at 7:32:20 AM, Osipov Michael (micha...@apache.org) wrote:
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348853
There are still a
I remember working with Stephen on this.
I think the related issues were MNG-6209, MNG-6275
Stephen wrote a small integration test to show which extensions were visible to
who and in which order.
It showed there are some edge cases that didn't work as expected.
However, I can't find that project
28 matches
Mail list logo
