- This topic has 3 replies, 3 voices, and was last updated 13 years, 3 months ago by giofyxle.
-
AuthorPosts
-
giofyxleMemberHallo Myeclipse Users,
In my pom.xml I have configured <uniqueVersion>false</uniqueVersion> in order to install my snapshot-artifacts with short names into nexus:
<distributionManagement> <snapshotRepository> <id>safir.snapshot.nexus</id> <url>http://dev-server2:8081/nexus/content/repositories/snapshots</url> <uniqueVersion>false</uniqueVersion> </snapshotRepository> </distributionManagement>
So calling maven from the console with
mvn -B -s C:\Users\georg.SAFIR-WID\.m2\settings.xml deploy
produces the expected files
artifact-version-SNAPSHOT.jar
and
artifact-version-SNAPSHOT-sources.jar
and installs it to my nexus database.
Calling the same from myeclipse the flag <uniqueVersion>false</uniqueVersion> seems to be ignored. Then the artifacts will be installed to nexus with names extended by timestamps:
artifact-version-20110819.081635-3.jar
and
artifact-version-20110819.081635-3-sources.jar
What I am doing wrong?
Unfortunately the artifacts with timestamp-extended names don’t fit to my EAR deployment. 🙁
Thanks in advance,
Gio
support-swapnaModeratorgiofyxle ,
Sorry for the delay. I have escalated it to a dev team member to look into it.
They will get back to you. Sorry for the inconvenience caused.
support-tomaszMemberAre You using the same mvn version from console and from MyEclipse? It is possible verify this under Window-> Preferences -> Maven -> Installations.
giofyxleMemberhallo tomasz,
I thought I would use the same version, but at a second glance I saw I didn’t.
And this is the solution:With Maven 2.2.1 it will work as I wanted.
Maybe for other Users the following will be interesting:
On
/Window/Preferences/MyEclipse/Maven4MyExclispe/Maven/Installations
I added and selected my maven installation of version 2.2.1.But this was not enough!
When starting a maven-job from MyEclipse, once more there is a setting for the maven runtime. (right mouse click on project/Run As/Run Configurations) or (right mouse click on project/Debug As/Debug Configurations).
Here I had to select once more the maven runtime of version 2.2.1.Now everthing works like I expected.
Thanks! -
AuthorPosts