Re: [VOTE] Release Maven Resolver version 1.6.1
+1 none-binding However, I still see random compilation failure at my multiple thread build. I am hoping the latest maven-resolver would make it go away :-) Thanks -D On Sun, Oct 4, 2020 at 3:16 PM Hervé BOUTEMY wrote: > +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 still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissue > > s > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1607/ > > > https://repository.apache.org/content/repositories/maven-1607/org/apache/mav > > en/resolver/maven-resolver/1.6.1/maven-resolver-1.6.1-source-release.zip > > > > Source release checksum(s): > > maven-resolver-1.6.1-source-release.zip > > > ab45c772e9af4061977feb4fb48e3ae9ddd8cbebe41ada40f2a762504e96fd4c0fd4a939ab70 > > 7667d9888caf92ab9fa354abe0624031c7049b7a2cb133421ddd > > > > Staging site: > > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Note: This Resolver offers salvation from a 13.5 years old feature > > request: MNG-2802 > > Yes, you can have now concurrent-safe access to your local Maven > > repository synchronized with Redis. > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [maven-resolver] branch master updated (aa5e9b1 -> b85faae)
moving the plugin to release profile, then have a release build different from the usual SNAPSHOT build does not look a good idea if we need to avoid building with JDK 7 because JDK 8 is required, it's up to Jenkins file to select We already do that for Maven Artifact Transfer for example https://github.com/apache/maven-artifact-transfer/blob/master/Jenkinsfile Le dimanche 4 octobre 2020, 20:37:55 CEST micha...@apache.org a écrit : > This is an automated email from the ASF dual-hosted git repository. > > michaelo pushed a change to branch master > in repository https://gitbox.apache.org/repos/asf/maven-resolver.git. > > > from aa5e9b1 [maven-release-plugin] prepare for next development > iteration add b85faae Move OSGi metadata generation to apache-release > profile > > No new revisions were added by this update. > > Summary of changes: > maven-resolver-api/pom.xml | 162 ++--- > maven-resolver-connector-basic/pom.xml | 240 ++-- > maven-resolver-impl/pom.xml | 264 +++--- > maven-resolver-spi/pom.xml | 159 ++--- > maven-resolver-synccontext-global/pom.xml | 36 +-- > maven-resolver-synccontext-redisson/pom.xml | 36 +-- > maven-resolver-test-util/pom.xml| 167 +++--- > maven-resolver-transport-classpath/pom.xml | 222 +- > maven-resolver-transport-file/pom.xml | 232 ++- > maven-resolver-transport-http/pom.xml | 338 > ++-- maven-resolver-transport-wagon/pom.xml | > 284 --- maven-resolver-util/pom.xml | > 169 +++--- > pom.xml | 25 +- > 13 files changed, 1208 insertions(+), 1126 deletions(-) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo commented on pull request #208: fix broken links at /maven-logging.html
elharo commented on pull request #208: URL: https://github.com/apache/maven-site/pull/208#issuecomment-703898696 Thanks! 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 the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo merged pull request #208: fix broken links at /maven-logging.html
elharo merged pull request #208: URL: https://github.com/apache/maven-site/pull/208 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 the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] slawekjaranowski opened a new pull request #208: fix broken links at /maven-logging.html
slawekjaranowski opened a new pull request #208: URL: https://github.com/apache/maven-site/pull/208 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 the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Hacktoberfest
After reading the DigitalOcean update again, I noticed that I made a little mistake in interpreting their rules. From the contributor perspective, PRs count if: Submitted during the month of October AND ( The PR is labelled as hacktoberfest-accepted by a maintainer OR Submitted in a repo with the hacktoberfest topic AND ( The PR is merged OR The PR has been approved ) ) So even if we do not opt in, we could still label any valuable contribution with 'hacktoberfest-accepted' and it would count towards the "t-shirt or tree" goal. Sure, we could debate whether that should be the only reason for people to contribute, but I think that's another question. For now, I think opting our repositories in is NOT the right thing to do. Repositories that have the hacktoberfest topic are likely to attract spam (since having it merged or accepted counts towards the Hacktoberfest goal). We could still label a valuable contribution with 'hacktoberfest-accepted' - no cost on our side, potentially happy contributor elsewhere. Thanks, Maarten On 05/10/2020 13:58, Martin Kanters wrote: I think this is a nice opportunity to get more people onboard and I am willing to spend more time reviewing PRs this month. As Maarten mentions, we do not have to have all PRs finished in October, they only have to be marked as 'hacktoberfest-accepted' so that gives us extra time. I do agree it would be nice to have an up-to-date up-for-grabs list as Gary mentions, so we should check the current up-for-grabs JIRA issues. Martin Op zo 4 okt. 2020 om 20:49 schreef Michael Osipov : 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 stay unanswered. IF we would also join hacktober, we must change those priorities for a month and focus on that, maybe even using the time to respond the open PRs. thanks, Robert On 4-10-2020 13:36:52, Markus KARG wrote: 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 Mulders; dev@maven.apache.org Betreff: Re: Hacktoberfest 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 explicitly say the will pick up these PR with the highest priority for 1 month. Otherwise I'd say no. Robert On 3-10-2020 20:41:04, Maarten Mulders wrote: Hi all, Today, I came across this update [1] from DigitalOcean, one of the companies behind Hacktoberfest. TL;DR: to prevent "spam pull requests", only accepted/merged/approved pull requests against GitHub repositories labelled "hacktoberfest" qualify for the free t-shirt or planting a tree. This is other than previous years, where _every_ pull request would qualify, even if the repository owner did not explicitly participate in Hacktoberfest. I would argue it makes sense to opt-in Maven repositories for Hacktoberfest. If it could encourage people to start contributing to Maven, I think that would be useful. It might also bring Maven to the attention of people who are looking for (Java) projects to contribute to. Any thoughts? Thanks, Maarten [1] https://hacktoberfest.digitalocean.com/hacktoberfest-update - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: (un)stable builds and Java upgrade
Maarten and I took a look at the failing projects today and have restored the matrix of JDKs and Maven versions in the Jenkins pipelines. Windows hosts apparently do not have JDK 16 installed. I've added a comment in INFRA-20576 [1]. "maven-wagon" was failing because of recent changes to the Jenkins pipeline and after fixing that they are green again [2]. "maven-common-artifact-filters" started working again after a re-run [3]. I hope it's not flaky, but rather hope that the recent Jenkinsfile changes have fixed the issue. "maven-source-plugin" is indeed waiting on a new release of plexus-archiver. Martin [1] https://issues.apache.org/jira/browse/INFRA-20576 [2] https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-wagon/job/master/31/ [3] https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-common-artifact-filters/job/master/25/ Op vr 2 okt. 2020 om 13:44 schreef Robert Scholte : > Now that Java 15 is the latest release and Java 16-ea is available, we > should upgrade that on our Jenkins server[1][2] (I see somebody reduced the > number of versions, we shouldn't do that!) > However, as long as we don't have our builds stable, we can't be sure if > the Java upgrade has a negative effect on these builds. > > I thought I'd checked it a week ago and it really looks like we have new > failing projects.[3] > Please keep checking Jenkins when committing or merging to master. > > AFAIK maven-source-plugin is running too fast, exposing a bug in > Linux+Java8, fix is ready in plexus-archiver. > Wagon was failing on Windows due to long paths, now it is failing on > Linux!? > > The rest needs to be investigated. > > thanks, > Robert > > > [1] > https://github.com/apache/maven-jenkins-lib/blob/master/vars/asfMavenTlpStdBuild.groovy#L36-L37 > > [2] > https://github.com/apache/maven-jenkins-lib/blob/master/vars/asfMavenTlpPlgnBuild.groovy#L36-L37 > [3] > https://ci-builds.apache.org/job/Maven/job/dist-tool-plugin/job/master/site/dist-tool-master-jobs.html >
[GitHub] [maven-site] elharo opened a new pull request #207: clean up language
elharo opened a new pull request #207: URL: https://github.com/apache/maven-site/pull/207 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 the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Hacktoberfest
I think this is a nice opportunity to get more people onboard and I am willing to spend more time reviewing PRs this month. As Maarten mentions, we do not have to have all PRs finished in October, they only have to be marked as 'hacktoberfest-accepted' so that gives us extra time. I do agree it would be nice to have an up-to-date up-for-grabs list as Gary mentions, so we should check the current up-for-grabs JIRA issues. Martin Op zo 4 okt. 2020 om 20:49 schreef Michael Osipov : > 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 stay unanswered. > > IF we would also join hacktober, we must change those priorities for a > month and focus on that, maybe even using the time to respond the open PRs. > > > > thanks, > > Robert > > > > On 4-10-2020 13:36:52, Markus KARG wrote: > > 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 Mulders; dev@maven.apache.org > > Betreff: Re: Hacktoberfest > > > > 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 explicitly say the will pick > up these PR with the highest priority for 1 month. > > Otherwise I'd say no. > > > > Robert > > > > > > On 3-10-2020 20:41:04, Maarten Mulders wrote: > > Hi all, > > > > Today, I came across this update [1] from DigitalOcean, one of the > > companies behind Hacktoberfest. TL;DR: to prevent "spam pull requests", > > only accepted/merged/approved pull requests against GitHub repositories > > labelled "hacktoberfest" qualify for the free t-shirt or planting a > > tree. This is other than previous years, where _every_ pull request > > would qualify, even if the repository owner did not explicitly > > participate in Hacktoberfest. > > > > I would argue it makes sense to opt-in Maven repositories for > > Hacktoberfest. If it could encourage people to start contributing to > > Maven, I think that would be useful. It might also bring Maven to the > > attention of people who are looking for (Java) projects to contribute to. > > > > Any thoughts? > > > > Thanks, > > > > Maarten > > > > > > > > [1] https://hacktoberfest.digitalocean.com/hacktoberfest-update > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
