dependabot[bot] opened a new pull request #234:
URL: https://github.com/apache/maven-site/pull/234
Bumps ant from 1.10.9 to 1.10.10.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.ant:ant&package-ma
All of those tests seem to follow the process of starting a server at
port 0 indeed. Some tests even start two servers in one test:
MavenITmng4991NonProxyHostsTest and MavenITmng2387InactiveProxyTest. And
in all three scenarios they use
`InetAddress.getLocalHost().getCanonicalHostName()` to loo
dependabot[bot] opened a new pull request #60:
URL: https://github.com/apache/maven-doxia/pull/60
Bumps ant-apache-regexp from 1.10.9 to 1.10.10.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.ant:a
dependabot[bot] opened a new pull request #11:
URL: https://github.com/apache/maven-doxia-site/pull/11
Bumps ant from 1.10.9 to 1.10.10.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.ant:ant&packag
dependabot[bot] opened a new pull request #47:
URL: https://github.com/apache/maven-site-plugin/pull/47
Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver)
from 4.2.4 to 4.2.5.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-archiver/re
yes, there was one more issue with host.
I also had to turn "localhost" to 127.0.0.1 in the socket.
T
On Sun, Apr 18, 2021 at 11:48 PM Olivier Lamy wrote:
> Hi,
> Do not change ports or use hard coded ports.
> The current ITs are using port 0 which means Jetty will allocate a
> random available
Hi,
Do not change ports or use hard coded ports.
The current ITs are using port 0 which means Jetty will allocate a
random available port.
There must be some problems with host lookup. In some environments (such as
kubernetes) using localhost or 127.0.0.1 can be problematic.
What is the error?
Wha
I had exactly the same problem and I added one more step to the CI which
checked all open ports.
For instance they changed something in Github and 8081 or 8082 was
allocated.
There was a conflict with the ports and I had to shift mine, that;s it.
T
On Sun, Apr 18, 2021 at 8:17 PM Maarten Mulders
Hi all,
Back on this topic - which prepares v4 releases too btw.
What do we finally write?
That maven will always fix the latest (stable) version and can release
maintenance branches on demands (lazily)?
Do we write 3.6 and 4 are active and maintained branches currently or do we
drop 3.x with f
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%20AND%20resolution%20%3D%20Unresolved%20ORDER%20B
Hi all,
It seems the following IT's predictably fail on Linux (not on Windows or
MacOS) in GitHub Actions, but not at all in Jenkins:
* MavenIT0146InstallerSnapshotNaming
* MavenITmng2387InactiveProxyTest
* MavenITmng4991NonProxyHostsTest
This is also the case in master, by the way. What they
11 matches
Mail list logo