You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(3.8.6) on a *-SNAPSHOT project using nexus-staging-maven-plugin will deploy snapshots with two different versions (…-1 and …-2), as expected. But
mvnd deploy
# edit some file
mvnd deploy
(0.7.1) seems to redeploy the same timestamped version (…-1). Maybe whatever inside Maven holds a consistent version number across reactor modules (recently added) is improperly being cached?
The text was updated successfully, but these errors were encountered:
Fwiw, the nexus-staging-maven-plugin uses very old maven api, I would advise to switch to the standard deploy plugin instead.
Also a way to reproduce the problem would be required to identify where the problem comes from.
the nexus-staging-maven-plugin uses very old maven api
OK, then unclear where fault may lie. Timestamped snapshots are always a mess anyway. CC @stephenc@jtnord
switch to the standard deploy plugin
Not an option if you need to automate interactions with Nexus I am afraid—opening a staging repository, grouping changes, closing it, promoting it to release.
mvn deploy # edit some file mvn deploy
(3.8.6) on a
*-SNAPSHOT
project usingnexus-staging-maven-plugin
will deploy snapshots with two different versions (…-1
and…-2
), as expected. Butmvnd deploy # edit some file mvnd deploy
(0.7.1) seems to redeploy the same timestamped version (
…-1
). Maybe whatever inside Maven holds a consistent version number across reactor modules (recently added) is improperly being cached?The text was updated successfully, but these errors were encountered: