[MDEP-691] useBaseVersion ignored when resolving artifacts from local repository (works from remote)

[jira-importer]

Jakub Bochenski opened MDEP-691 and commented

Please compare the results. -Psonatype enables remote sonatype snapshots repository.

$ mvn   dependency:copy -Dartifact=com.trello.identifier:package-identifier:0.0.2-SNAPSHOT -Psonatype -U -Dmdep.useBaseVersion=false | grep Copying
[INFO] Copying package-identifier-0.0.2-SNAPSHOT.jar to /home/bochja/${project.basedir}/target/dependency/package-identifier-0.0.2-20190311.143402-1.jar
$ rm -rf '/home/bochja/${project.basedir}/target/dependency'
$ mvn   dependency:copy -Dartifact=com.trello.identifier:package-identifier:0.0.2-SNAPSHOT -Psonatype -U -Dmdep.useBaseVersion=true | grep Copying
[INFO] Copying package-identifier-0.0.2-SNAPSHOT.jar to /home/bochja/${project.basedir}/target/dependency/package-identifier-0.0.2-SNAPSHOT.jar
$ rm -rf '/home/bochja/${project.basedir}/target/dependency'
$ mvn   dependency:copy -Dartifact=com.trello.identifier:package-identifier:0.0.2-SNAPSHOT -o -Dmdep.useBaseVersion=true | grep Copying
[INFO] Copying package-identifier-0.0.2-SNAPSHOT.jar to /home/bochja/${project.basedir}/target/dependency/package-identifier-0.0.2-SNAPSHOT.jar
$ rm -rf '/home/bochja/${project.basedir}/target/dependency'
$ mvn   dependency:copy -Dartifact=com.trello.identifier:package-identifier:0.0.2-SNAPSHOT -o -Dmdep.useBaseVersion=false | grep Copying
[INFO] Copying package-identifier-0.0.2-SNAPSHOT.jar to /home/bochja/${project.basedir}/target/dependency/package-identifier-0.0.2-SNAPSHOT.jar
$ ls ~/.m2/repository/com/trello/identifier/package-identifier/0.0.2-SNAPSHOT/
maven-metadata-sonatype.xml  maven-metadata-sonatype.xml.sha1  package-identifier-0.0.2-20190311.143402-1.jar  package-identifier-0.0.2-20190311.143402-1.jar.sha1  package-identifier-0.0.2-SNAPSHOT.jar  _remote.repositories  resolver-status.properties

---

No further details from MDEP-691

[jira-importer]

Karl Heinz Marbaise commented

Can you please make a full example and show the behavour you have and what you like to see.

[jira-importer]

Jakub Bochenski commented

I just run ```
mvn dependency:copy -Dartifact=${artifact} -Dmdep.useBaseVersion=true|false

Regardless of the setting I get a file with 1-SNAPSHOT version, instead of a timestamped snapshot version. 

[jira-importer]

Karl Heinz Marbaise commented

Why do you like to have the timestamped version instead? If you like to lock that version to the timestamped you should use https://www.mojohaus.org/versions-maven-plugin/lock-snapshots-mojo.html ? If you use the timestamped version which looks like this: 1.0-20090128.202731-1 which is no longer a SNAPSHOT versions...

[jira-importer]

Jakub Bochenski commented

I'm just trying to grab a single file and get it's timestamped version in the filename.

[jira-importer]

Jakub Bochenski commented

The dependency:copy goal doesn't work for project dependencies in the first place, that would be dependency:copy-dependencies

[jira-importer]

Karl Heinz Marbaise commented

Sorry but that does not answer my question: What is the purpose of using a timestamped version? Would it be sufficient to use stripVersion? Furthermore I'm asking cause I try to understand what kind of use case you have. Best would be explain the project you have and why you need to use maven-dependency-plugin:copy...?

[jira-importer]

Jakub Bochenski commented

I want the timestamped version because I need the timestamp. If you really need to know that the purpose is to deploy the file as an AWS lambda function and unique filenames help us keep track of the version.

Now after some further testing I realized the problem seems to occur when resolving the artifact from local repository. It works as expected when using remote.

[jira-importer]

Jakub Bochenski commented

I think in the end it boils down to the presence of groupId/artifactId/version-SNAPSHOT/maven-metadata.xml
Typically this file is included in remote repositories, but its not present in the local repository for some reason.
Instead there are files like groupId/artifactId/version-SNAPSHOT/maven-metadata-REPOSITORY_ID.xml but the code that tries to resolve the version fails to read those.

[alan-czajkowski]

when I use the dependency:copy goal with useBaseVersion flag set to true:
(Maven Dependency plugin version: 3.9.0)

$ mvn dependency:copy -Dartifact="groupId:artifactId:1.2.3-SNAPSHOT:tar.gz:deploy" \
                      -DuseBaseVersion=true \
                      -DoverWriteSnapshots=true \
                      -DoutputDirectory="." \
                      --no-transfer-progress

file system:

artifactId-1.2.3-20260302.141819-5-deploy.tar.gz

it still places the file on the file system with a timestamped SNAPSHOT, how do I get the file name to use 1.2.3-SNAPSHOT explicitly in the filename (instead of the timestamp) when using this goal?

@khmarbaise ?

[alan-czajkowski]

@khmarbaise any ideas on the above comment?

[wilx]

when I use the dependency:copy goal with useBaseVersion flag set to true: (Maven Dependency plugin version: 3.9.0)

$ mvn dependency:copy -Dartifact="groupId:artifactId:1.2.3-SNAPSHOT:tar.gz:deploy" \
                      -DuseBaseVersion=true \
                      -DoverWriteSnapshots=true \
                      -DoutputDirectory="." \
                      --no-transfer-progress

file system:

artifactId-1.2.3-20260302.141819-5-deploy.tar.gz

it still places the file on the file system with a timestamped SNAPSHOT, how do I get the file name to use 1.2.3-SNAPSHOT explicitly in the filename (instead of the timestamp) when using this goal?

@khmarbaise ?

You are using wrong property. It is mdep.useBaseVersion.

[wilx]

I can't reproduce the OP's issue. I suggest closing, unless there is a good reproducer.