Troubleshooting switch to Red Hat Online Maven Repository

Updated

Red Hat Online Maven repository contains artifacts that have been published for all product releases. If you’ve been using ZIP repositories in the past, you might experience slight differences in artifact content. Except for a few exceptions mentioned in this document, these differences will not have any effect on functionality of the application.

Maven artifacts in ZIP and online repository have different checksums

Depending on the checksum policy you have set in your settings.xml file, it might happen that Maven will complain and refuse to continue with the build. The reason for that can be different build time, jdk version or checksum of generated code.

The checksum policy can be set to to ignore, warn or fail values for each of the repositories. To ensure reproducibility and security of the build, we recommend you to either use warn policy and analyse results or stick with fail policy.

Solution
Clean your local repository that might contains cached artifacts from ZIP files you’ve been using in the past. This repository is usually located in $USER_DIR/.m2/repository or the location depends on actual value in settings.xml file.

If you are using your Maven own repository manager, make sure that you remove all repositories that are based on content of ZIP repositories.

Signed artifacts
Signed artifacts can have an effect on the performance of your application or might lead to issues while bytecode modification libraries are in use.

Solution
First, your solution for different checksum problems to make sure you are using artifacts from Online repository. Afterwards, if you encounter any of the issues with unsigned artifacts in Red Hat Maven Online repository, please contact support team.

Different artifacts
There are few artifacts distributed in Red Hat Maven Online repository that contain different content than artifacts from ZIP repositories. All these artifacts represent newer artifact releases, hence you could experience different behavior.

Solution
First, identify dependencies that are in use of your application. You can use mvn dependency:tree to list all dependencies of your application.
Alternatively, you can check content of the artifacts and find affected filenames.

Then identify if you are using any of the artifacts from list below (artifacts coordinates are specified in groupId:artifactId:packagingType:version format):

org.jboss.as:jboss-as-cli:jar:7.4.3.Final-redhat-2  or jboss-as-cli-7.4.3.Final-redhat-2-client.jar file
org.jboss.as:jboss-as-clustering-infinispan:jar:7.1.3.Final-redhat-4 or jboss-as-clustering-infinispan-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-clustering-jgroups:jar:7.1.3.Final-redhat-4 or jboss-as-clustering-jgroups-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-clustering-web-spi:jar:7.1.3.Final-redhat-4 or jboss-as-clustering-web-spi-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-connector:jar:7.1.3.Final-redhat-4 or jboss-as-connector-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-controller-client:jar:7.1.3.Final-redhat-4 or jboss-as-controller-client-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-controller-client:jar:7.4.3.Final-redhat-2 or jboss-as-controller-client-7.4.3.Final-redhat-2.jar file
org.jboss.as:jboss-as-deployment-repository:jar:7.1.3.Final-redhat-4 or jboss-as-deployment-repository-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-ejb3:jar:7.1.3.Final-redhat-4 or jboss-as-ejb3-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-embedded:jar:7.1.3.Final-redhat-4 or jboss-as-embedded-7.1.3.Final-redhat-4.jar
org.jboss.as:jboss-as-jacorb:jar:7.1.3.Final-redhat-4 or jboss-as-jacorb-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-jmx:jar:7.1.3.Final-redhat-4 or jboss-as-jmx-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-jpa-spi:jar:7.1.3.Final-redhat-4 or jboss-as-jpa-spi-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-naming:jar:7.1.3.Final-redhat-4 or jboss-as-naming-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-network:jar:7.1.3.Final-redhat-4 or jboss-as-network-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-platform-mbean:jar:7.1.3.Final-redhat-4 or jboss-as-platform-mbean-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-process-controller:jar:7.1.3.Final-redhat-4 or jboss-as-process-controller-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-protocol:jar:7.1.3.Final-redhat-4 or jboss-as-protocol-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-protocol:jar:7.4.3.Final-redhat-2 or jboss-as-protocol-7.4.3.Final-redhat-2.jar file
org.jboss.as:jboss-as-remoting:jar:7.1.3.Final-redhat-4 or jboss-as-remoting-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-security:jar:7.1.3.Final-redhat-4 or jboss-as-security-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-threads:jar:7.1.3.Final-redhat-4 or jboss-as-threads-7.1.3.Final-redhat-4.jar file
org.jboss.as:jboss-as-transactions:jar:7.1.3.Final-redhat-4 or jboss-as-transactions-7.1.3.Final-redhat-4.jar file
org.jboss.javaee: jboss-ejb-api:3.0.0.GA or jboss-ejb-api-3.0.0.GA.jar file
org.jboss.seam:seam-cdk-helper:jar:1.0-redhat-1 or seam-cdk-helper-1.0-redhat-1.jar file
org.jboss.test-jsf:maven-mockgenerator-plugin:jar:1.1.2-redhat-1 or maven-mockgenerator-plugin-1.1.2-redhat-1.jar file
org.richfaces.build.resources:faces-shade-transformers:jar:8-redhat-1 or faces-shade-transformers-8-redhat-1.jar file
org.richfaces:richfaces-build-checkstyle:jar:5-redhat-2 or  richfaces-build-checkstyle-5-redhat-2.jar file

If any of these artifacts matches, make sure that you have cleared both your local repository cache and any cache that might be present in your company Maven repository cache / manager. If you happen to experience any build or runtime issues with your application rebuilt to use artifact from Red Hat Online Maven Repository, please contact support.

Product(s)
Category
Article Type