[ANN] Maven Javadoc Plugin 3.7.0 released
The Apache Maven team is pleased to announce the release of the Maven Javadoc Plugin, version 3.7.0. This module generates browsable HTML pages from Java source code. https://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-javadoc-plugin 3.7.0 Release Notes - Maven Javadoc Plugin - Version 3.7.0 ** Bug * [MJAVADOC-793] - java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null ** Dependency upgrade * [MJAVADOC-788] - Upgrade commons-io:commons-io to 2.16.0 * [MJAVADOC-789] - Upgrade org.codehaus.plexus:plexus-interactivity-api to 1.3 * [MJAVADOC-795] - Upgrade to Parent 42 and Maven 3.6.3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Site Plugin 4.0.0-M15 released
The Apache Maven team is pleased to announce the release of the Maven Site Plugin, version 4.0.0-M15. https://maven.apache.org/plugins/maven-site-plugin/ Release Notes - Maven Site Plugin - Version 4.0.0-M15 ** Dependency upgrade * [MSITE-1008] - Upgrade to Parent 42 and Maven 3.6.3 * [MSITE-1009] - Upgrade plugins and components (in ITs) Please also note for this new major version: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Plugin Tools 3.13.1 released
The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Tools, version 3.13.1. https://maven.apache.org/plugin-tools/ Release Notes - Maven Plugin Tools - Version 3.13.1 ** Task * [MPLUGIN-526] - Clean up dependencies reported by dependencies:analyze Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
On 31/05/2024 17:11, Tamás Cservenák wrote: And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 Regarding this issue, I don't know where is the best place to raise it but there are 3 contexts: - IPv4-only - dual-stack - and ... IPv6-only because this comment [1]seems to not consider the last case. 1. https://bugs.openjdk.org/browse/JDK-8311547?focusedId=14594731=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14594731 -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
Hi, On 31/05/2024 17:11, Tamás Cservenák wrote: And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 and read about java.net.preferIPv6Addresses Java system property... Also, try to invoke Maven as: MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X Thanks for the pointer. It solved the issue on transfer. I have a compilation failure now but I guess it's now related to missing packages on my side. Regarding my version of Maven, I tend to stick to whatever the operating system have in the main repository. I will upgrade at least to debian 12 ; it comes with maven 3.8.7 [1] . But once again, thank you. 1. https://packages.debian.org/bookworm/maven -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
And read this as well, Java is nicely covered: https://www.reddit.com/r/ipv6/comments/scvuy0/what_devices_do_you_know_of_that_dont_support/ T On Fri, May 31, 2024 at 3:11 PM Tamás Cservenák wrote: > And one more hint: > > See https://bugs.openjdk.org/browse/JDK-8311547 > and read about java.net.preferIPv6Addresses Java system property... > > Also, try to invoke Maven as: > MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X > > (to pass to JVM to prefer IPv6 addresses) > > Thanks > T > > On Fri, May 31, 2024 at 3:02 PM Tamás Cservenák > wrote: > >> Howdy, >> >> Unsure why, but: >> - you use Maven 3.6.3 while the latest (bugfix) release is 3.9.7. A LOT >> (especially transfer) related bugs were fixed down the road since 3.6.3. >> - due 3.6.3 you use (probably old) Wagon transfer, that on the other hand >> relies on (probably old) Apache HttpClient >> - still, it seems Java TCP stack have issues to use your network as >> stated in cause "java.net.SocketException: Network is unreachable (connect >> failed)" >> - you should verify is Java capable at all to use your network, as if it >> cannot, Maven hardly can help here. >> >> Google for Java and IPv6 as there are a lot of SO and other hits that >> showcases how to figure out (using Java simple code snippets) what may be >> the problem. >> >> Thanks >> T >> >> On Fri, May 31, 2024 at 2:37 PM Willy Manga wrote: >> >>> Hi, >>> >>> >>> I want to build guacamole-client as explained in the mainstream >>> repository[0] but the transfer failed as you can see here[1]. >>> >>> My environment: >>> - maven 3.6.3-5 (running on debian 11) >>> - IPv6-only with a NAT64 gateway in the network. >>> >>> >>> Someone in the guacamole user mailing-list suggested it might be an >>> issue with how either my network is setup or "some java incompatibilty" >>> [2] . >>> >>> I don't see on my side what can be wrong with the network. I was able to >>> retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I >>> don't know if during the execution of 'mvn package' something is pulling >>> resource from a hard-coded address. If that's the case it can explained >>> the failure. >>> >>> Any guidance appreciated. >>> >>> Thanks. >>> >>> >>> 0. https://github.com/apache/guacamole-client >>> >>> 1. http://paste.debian.net/1318665/ >>> >>> 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms >>> >>> >>> -- >>> Willy Manga >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>>
Re: Transfer failed in an IPv6-only (+NAT64) environment
And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 and read about java.net.preferIPv6Addresses Java system property... Also, try to invoke Maven as: MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X (to pass to JVM to prefer IPv6 addresses) Thanks T On Fri, May 31, 2024 at 3:02 PM Tamás Cservenák wrote: > Howdy, > > Unsure why, but: > - you use Maven 3.6.3 while the latest (bugfix) release is 3.9.7. A LOT > (especially transfer) related bugs were fixed down the road since 3.6.3. > - due 3.6.3 you use (probably old) Wagon transfer, that on the other hand > relies on (probably old) Apache HttpClient > - still, it seems Java TCP stack have issues to use your network as stated > in cause "java.net.SocketException: Network is unreachable (connect failed)" > - you should verify is Java capable at all to use your network, as if it > cannot, Maven hardly can help here. > > Google for Java and IPv6 as there are a lot of SO and other hits that > showcases how to figure out (using Java simple code snippets) what may be > the problem. > > Thanks > T > > On Fri, May 31, 2024 at 2:37 PM Willy Manga wrote: > >> Hi, >> >> >> I want to build guacamole-client as explained in the mainstream >> repository[0] but the transfer failed as you can see here[1]. >> >> My environment: >> - maven 3.6.3-5 (running on debian 11) >> - IPv6-only with a NAT64 gateway in the network. >> >> >> Someone in the guacamole user mailing-list suggested it might be an >> issue with how either my network is setup or "some java incompatibilty" >> [2] . >> >> I don't see on my side what can be wrong with the network. I was able to >> retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I >> don't know if during the execution of 'mvn package' something is pulling >> resource from a hard-coded address. If that's the case it can explained >> the failure. >> >> Any guidance appreciated. >> >> Thanks. >> >> >> 0. https://github.com/apache/guacamole-client >> >> 1. http://paste.debian.net/1318665/ >> >> 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms >> >> >> -- >> Willy Manga >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >>
Re: Transfer failed in an IPv6-only (+NAT64) environment
Howdy, Unsure why, but: - you use Maven 3.6.3 while the latest (bugfix) release is 3.9.7. A LOT (especially transfer) related bugs were fixed down the road since 3.6.3. - due 3.6.3 you use (probably old) Wagon transfer, that on the other hand relies on (probably old) Apache HttpClient - still, it seems Java TCP stack have issues to use your network as stated in cause "java.net.SocketException: Network is unreachable (connect failed)" - you should verify is Java capable at all to use your network, as if it cannot, Maven hardly can help here. Google for Java and IPv6 as there are a lot of SO and other hits that showcases how to figure out (using Java simple code snippets) what may be the problem. Thanks T On Fri, May 31, 2024 at 2:37 PM Willy Manga wrote: > Hi, > > > I want to build guacamole-client as explained in the mainstream > repository[0] but the transfer failed as you can see here[1]. > > My environment: > - maven 3.6.3-5 (running on debian 11) > - IPv6-only with a NAT64 gateway in the network. > > > Someone in the guacamole user mailing-list suggested it might be an > issue with how either my network is setup or "some java incompatibilty" > [2] . > > I don't see on my side what can be wrong with the network. I was able to > retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I > don't know if during the execution of 'mvn package' something is pulling > resource from a hard-coded address. If that's the case it can explained > the failure. > > Any guidance appreciated. > > Thanks. > > > 0. https://github.com/apache/guacamole-client > > 1. http://paste.debian.net/1318665/ > > 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms > > > -- > Willy Manga > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Transfer failed in an IPv6-only (+NAT64) environment
Hi, I want to build guacamole-client as explained in the mainstream repository[0] but the transfer failed as you can see here[1]. My environment: - maven 3.6.3-5 (running on debian 11) - IPv6-only with a NAT64 gateway in the network. Someone in the guacamole user mailing-list suggested it might be an issue with how either my network is setup or "some java incompatibilty" [2] . I don't see on my side what can be wrong with the network. I was able to retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I don't know if during the execution of 'mvn package' something is pulling resource from a hard-coded address. If that's the case it can explained the failure. Any guidance appreciated. Thanks. 0. https://github.com/apache/guacamole-client 1. http://paste.debian.net/1318665/ 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shade Plugin 3.6.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shade Plugin, version 3.6.0 This plugin provides the capability to package the artifact in an uber-jar, including its dependencies and to shade - i.e. rename - the packages of some of the dependencies. https://maven.apache.org/plugins/maven-shade-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-shade-plugin 3.6.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-shade-plugin/download.cgi Release Notes - Maven Shade Plugin - Version 3.6.0 ** Bug * [MSHADE-428] - Typo causes mysterious NPE in build ** New Feature * [MSHADE-478] - Add ability to inject extra artifacts into shaded output ** Task * [MSHADE-473] - Drop legacy and superfluous deps: maven-dependency-tree and commons-collections4 ** Dependency upgrade * [MSHADE-474] - Align dependencies with Maven 3 (as this is Maven3 plugin) * [MSHADE-475] - Upgrade commons-io to 2.16.1 * [MSHADE-476] - Upgrade commons-compress to 1.26.2 * [MSHADE-477] - (test) Upgrade test dependencies Have fun, -The Apache Maven team
