'Repository does not allow updating assets: talend-custom-libs-release' warning in Nexus log

Problem Description

Every time you restart Studio, connected to a remote project (Talend Administration Center) and configured with Nexus, the nexus.log file has a warning similar to the following:

2020-03-06 20:40:56,411+0530 WARN [qtp713962441-303] talend-custom-libs-admin org.sonatype.nexus.repository.view.handlers.ExceptionHandler - Illegal operation: PUT /org/talend/libraries/curator-client-2.6/6.0.0/curator-client-2.6-6.0.0.0: org.sonatype.nexus.repository.IllegalOperationException: Repository does not allow updating assets: talend-custom-libs-release

 

Root Cause

This is as expected. Every time Studio restarts, it has to connect to the Nexus server and sync all of the libraries from .m2.

Nexus_share_Libs (3).jpg

 

The cycle repeats for all of the Studio libraries present in .m2 and is synced based on the User Libraries configuration specified in the Talend Administration Center and thus Studio.

 

From the Nexus side, the warnings you are seeing are thrown because libraries might already exist. However, Studio does not upload the same libraries repeatedly in Nexus even though the logs show these warnings.

 

Solution

You can safely ignore these warnings.

 

Example

The curator-client-2.6.0 JAR file appears in the nexus.log after starting Studio connecting to Talend Administration Center.

nexus1.PNG

 

Notice that the same JAR exists in Nexus. However, it has a different time stamp than the nexus.log.

nexus2.PNG

 

This means even though the nexus.log is showing you those JARs, because Studio loads them during startup and checks with Nexus to manage the sync, the JARs already available in Nexus are not overwritten. Only the new JARs are uploaded.

Version history
Revision #:
4 of 4
Last update:
‎04-20-2020 07:29 AM
Updated by:
 
Contributors