Maven artifact dependency trigger unable to check for dependency updates to timestamped artifact

Avatar
Permanently deleted user
Created

I have a Maven Artifact Dependency Trigger configured like this:

However it results in this error from TeamCity:

It would appear that the trigger is looking in the correct path in Nexus for the artifact, but is not taking into account that the artifact has timestamp versions. ie http://<server>/nexus/content/repositories/snapshots/com/pb/bna/bna-client/1.0-SNAPSHOT/bna-client-1.0-20170728.144042-335.war exists in Nexus, whereas http://<server>/nexus/content/repositories/snapshots/com/pb/bna/bna-client/1.0-SNAPSHOT/bna-client-1.0-SNAPSHOT.war does not.

My understanding is that Maven 3 enforces timestamped artifact versions in Nexus - as mentioned here - https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-Non-uniqueSnapshotDeployments - so I can't turn this off. How do I configure the trigger to pick them up?

 

Votes

0

Share

7 comments
Avatar
Nikita Skvortsov
Created

Hi Sean,

Try using version range, e.g:
[0.9,)

0
Avatar
Permanently deleted user
Created

Thanks very much for responding. Unfortunately version of [0.9,) has the same result:

0
Avatar
Nikita Skvortsov
Created

Sorry for the delay. Can you attach the content of file in /nexus/content/repositories/snapshot/com/pb/bna/bna-rest/1.0-SNAPSHOT/maven-metadata.xml ?

0
Avatar
Permanently deleted user
Created

Here you go:

<metadata modelVersion="1.1.0">
<groupId>com.pb.bna</groupId>
<artifactId>bna-rest</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20170804.174446</timestamp>
<buildNumber>420</buildNumber>
</snapshot>
<lastUpdated>20170804174446</lastUpdated>
<snapshotVersions>
<snapshotVersion>
<extension>war</extension>
<value>1.0-20170804.174446-420</value>
<updated>20170804174446</updated>
</snapshotVersion>
<snapshotVersion>
<extension>pom</extension>
<value>1.0-20170804.174446-420</value>
<updated>20170804174446</updated>
</snapshotVersion>
<snapshotVersion>
<classifier>classes</classifier>
<extension>jar</extension>
<value>1.0-20170804.174446-420</value>
<updated>20170804174446</updated>
</snapshotVersion>
</snapshotVersions>
</versioning>
</metadata>

 

0
Avatar
Denis Lapuente
Created

Hi Sean,

That's rather strange, they should be picked up properly. Could you enable debug-all in "Administration" - "Diagnostics", then upload the new version to the maven repository, then wait for a check on the maven repository, then use the "Submit a request" button on top of this page to send us the teamcity-vcs.log and teamcity-server.log files.

0
Avatar
Permanently deleted user
Created

Hi Denis

I will try and get you these server diagnostics. Unfortunately I don't have permission to enable debug logging, so I will have to defer to the administrators of the TeamCity server.

Sean

0
Avatar
Permanently deleted user
Created

I've submitted a request with the server logs attached.

0

Please sign in to leave a comment.