Add maven-release-plugin about hotswapagent HOT 3 CLOSED

I am not sure about the issue, everything is 0.1-beta3 in current release.

Releases are done by:
mvn versions:set -DnewVersion=0.1-beta3 versions:commit

Is there any need for snapshot versions (0.1-SNAPSHOT?). It is useful for dependency management, but I suppose no one needs to link plugin as a dependency.

from hotswapagent.

Definitely snapshots are needed. Especially for us, developers, as right
now I have false version of 0.1-beta3 in my local repo since I was
experimenting without manually changing version.
Besides that, maven-release-plugin does great job in ensuring that no
snapshot dependencies get into release.
Other thing is that we can make it use "release" profile and put
maven-source-plugin only in that profile so that we save time during
regular development.

2014-05-08 7:58 GMT+02:00 Jiri Bubnik [email protected]:

I am not sure about the issue, everything is 0.1-beta3 in current release.

Releases are done by:
mvn versions:set -DnewVersion=0.1-beta3 versions:commit

Is there any need for snapshot versions (0.1-SNAPSHOT?). It is useful for
dependency management, but I suppose no one needs to link plugin as a
dependency.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-42515841
.

from hotswapagent.

Please create a pull request with this setup.

I was never successfull to create a convenient setup for multi module project with other dependent projects. On one hand I need to get new versions to developers quickly, on the other hand I don't want them to download twenty JARs on each startup.

from hotswapagent.