David Jencks wrote:
Would it be possible for the release plugin to do the following?1. modify working copy poms to release version 2. do a working copy to repo copy for the new tag3. adjust the working copy poms to the new version, or revert if the new version is the same as the old version4. commit the working copy poms if there is a new version. Is this process svn specific? If so could it be provided as an option?
I think the concept of tagging a working copy that *contains uncommitted changes* is svn specific.
Max.
signature.asc
Description: OpenPGP digital signature