Hi I am currently having a few issues which I don't quite seem to understand so I thought I'd ask around.
1 - If I have a project with a dependency on artifact A set to version 1.0.2-SNAPSHOT and I want to change that dependency to whatever last, non-snapshot, version can be found on my remote repository, it feels natural to me that running use-latest-releases should do the job however that mojo simply refuses to touch anything snapshot. When checking the code for the plugin it seems to actually be a design decision. Could anybody explain why is this the way it is and if there is any way around it? Running use-releases before it seems to do the job 2 - If I have dependency set to version 1.2.0-SNAPSHOT and version 1.2.0 is not deployed on my remote repository and I want to remove the snapshot from the version, I am inclined to believe that running use-releases mojo would do the job however it will simply refuse to do so if 1.2.0 is not deployed. All I want to do is remove the snapshot from it. This occurs due to issue number 1 mentioned above so if I can solve that this is less of an issue 3 - Last but not least I noticed that the update-parent mojo has a setting which allows you to set the version of the parent (parentVersion) however not matter how hard I try, the plugin seems to ignore that setting and set parent version to whatever is the latest from the remote repository even though the version I keep telling it to set is also deployed (Mind you the version is not a typical maven version pattern but my own). Regards ByteFlinger
