You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "nagrati (via GitHub)" <gi...@apache.org> on 2026/10/22 19:36:07 UTC
[PR] Fix Maven build warnings [accumulo]
nagrati opened a new pull request, #6606:
URL: https://github.com/apache/accumulo/pull/6606
Warnings during mvn package:
```
[WARNING] Unknown file extension: .../src/test/resources/org/apache/accumulo/core/accumulo.jceks
[WARNING] Unknown file extension: ../src/test/resources/org/apache/accumulo/core/empty.jceks
[WARNING] Unknown file extension: ../src/test/resources/org/apache/accumulo/core/passwords.jceks
[WARNING] Unknown file extension: ../src/test/resources/org/apache/accumulo/core/site-cfg.jceks
[WARNING] Unable to find a comment style definition for some files. You may want to add a custom mapping for the relevant file extensions.
[WARNING] Could not transfer metadata /.meta/prefixes.txt from/to jvnet-nexus-releases (https://maven.java.net/content/repositories/releases/): (certificate_expired) PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
```
Updated file path in pom.xml for excluding *.jecks files.
Added repositories and pluginRepositories blocks to pom.xml file for jvnet-nexus-releases to override the outdated references
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Fix Maven build warnings [accumulo]
Posted by "ctubbsii (via GitHub)" <gi...@apache.org>.
ctubbsii commented on code in PR #6606:
URL: https://github.com/apache/accumulo/pull/6606#discussion_r4354694426
##########
pom.xml:
##########
@@ -1836,4 +1836,30 @@ under the License.
</properties>
</profile>
</profiles>
+ <repositories>
+ <repository>
+ <id>jvnet-nexus-releases</id>
+ <name>jvnet-nexus-releases-override</name>
+ <url>https://apache.org</url>
+ <releases>
+ <enabled>true</enabled>
+ </releases>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ </repository>
+ </repositories>
+ <pluginRepositories>
+ <pluginRepository>
+ <id>jvnet-nexus-releases</id>
+ <name>jvnet-nexus-releases-override</name>
+ <url>https://apache.org</url>
+ <releases>
+ <enabled>true</enabled>
+ </releases>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ </pluginRepository>
+ </pluginRepositories>
Review Comment:
I've noticed with Maven 3.10.0, these seem to have started showing up, because 3.10 does some more aggressive checking for prefix files in all repositories it has detected anywhere in the dependency/plugin hierarchy, rather than limiting itself to only configured/active repositories. Some legacy artifacts seem to have POMs that point to these long-decommissioned repos. Maven 3.10 is now warning when it can't pull from it.
I'm not sure this is something that makes sense to add in our POM. It's probably something that is better to add to one's own personal settings.xml files, as in:
```xml
<mirrors>
<!-- Block jvnet-maven-releases -->
<mirror>
<id>block-jvnet-nexus-releases</id>
<mirrorOf>jvnet-nexus-releases</mirrorOf>
<name>Blocked jvnet-nexus-releases repository</name>
<url>http://0.0.0.0/</url>
<blocked>true</blocked>
</mirror>
</mirrors>
```
Let's leave this one out for now.
--
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.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org