Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1

+1 On Mon, 19 Apr 2021 at 05:12, Robert Scholte wrote: > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12344185&styleName=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=

Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1

+1 On 18-4-2021 21:12:47, Robert Scholte wrote: Hi, We solved 12 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12344185&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%

Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1

+1 On Sun, Apr 18, 2021 at 9:12 PM Robert Scholte wrote: > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12344185&styleName=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jq

Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1

Hi Andreas, thanks for testing, I really appreciate it! Regarding the voting, every vote counts, maybe especially from users. Depending on the release manager, their negative votes might result in the cancelling of the release. A few years ago we decided to drop the word "binding" during the vo

Re: Security/Versioning policy proposal

Le lun. 19 avr. 2021 à 17:20, Benjamin Marwell a écrit : > > Do we write 3.6 and 4 are active and maintained branches currently or > do we > > drop 3.x with first 4.x release? > > Dropping 3.x with the first 4.x release would not make sense from the > point you presented earlier. > I'd drop 3.x

Re: maven-site-plugin and sisu-inject-plexus

On Sat, 17 Apr 2021 at 13:47, Elliotte Rusty Harold wrote: > I'd certainly prefer to use a fully supported, maintained, and > documented framework instead of Plexus. So about Sisu: > Sisu is basically a few modules installed on top of Guice to make it more dynamic, plus a thin compatibility laye

Re: Security/Versioning policy proposal

> Do we write 3.6 and 4 are active and maintained branches currently or do we > drop 3.x with first 4.x release? Dropping 3.x with the first 4.x release would not make sense from the point you presented earlier. I'd drop 3.x as soon as we reach 4.1.0. > maintenance branches on demands My vote wo

[GitHub] [maven-doxia] asfgit closed pull request #60: Bump ant-apache-regexp from 1.10.9 to 1.10.10

asfgit closed pull request #60: URL: https://github.com/apache/maven-doxia/pull/60 -- 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

Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1

+1 Le dim. 18 avr. 2021 à 21:12, Robert Scholte a écrit : > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12344185&styleName=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?j

Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1

Hi, > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. just a user of the maven-jxr-plugin and not a committer, but I wanted to let you know anyway that version 3.1.1 works fine for me, even if I can

[GitHub] [maven-site] asfgit closed pull request #234: Bump ant from 1.10.9 to 1.10.10

asfgit closed pull request #234: URL: https://github.com/apache/maven-site/pull/234 -- 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

[GitHub] [maven-site] dependabot[bot] commented on pull request #234: Bump ant from 1.10.9 to 1.10.10

dependabot[bot] commented on pull request #234: URL: https://github.com/apache/maven-site/pull/234#issuecomment-822408264 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR and I'll res

Re: Failing IT's on Linux in GitHub Actions

yup definitely use loopback address (hostnames are not very reliable on such ephemeral nodes environments) On Mon, 19 Apr 2021 at 18:15, Tibor Digana wrote: > I had this problem with GH CI: > > java.net.BindException: Cannot assign requested address > at sun.nio.ch.Net.bind0(Native Method) > at

Re: Failing IT's on Linux in GitHub Actions

I had this problem with GH CI: java.net.BindException: Cannot assign requested address at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:461) at sun.nio.ch.Net.bind(Net.java:453) at sun.nio.ch.AsynchronousServerSocketChannelImpl.bind(AsynchronousServerSocketChannelImpl.java:16

Re: Failing IT's on Linux in GitHub Actions

Port 0 does not exist, only in your code. 0 means that a new unused local port is allocated. Again you have to use local loopback 127.0.0.1 as me. I had the same problem and I solved it. T On Mon, Apr 19, 2021 at 8:41 AM Maarten Mulders wrote: > All of those tests seem to follow the process of s

Re: Failing IT's on Linux in GitHub Actions

Hi Should we set java.net.preferIPv4Stack=true? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn