[
http://jira.codehaus.org/browse/MVERSIONS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246368#action_246368
]
Mario Zagar edited comment on MVERSIONS-68 at 12/3/10 6:33 PM:
---------------------------------------------------------------
We use TFS and have the same issue since TFS stores files as read-only until
they are explicity checked out.
This prevents me to use versions plugin efficiently since the process of
checking out all the poms on a multimodule project to remove read-only flag and
then modify them can be tiring.
In my case it would be enough to clear read-only flag on pom.xml and make it
writable before it is processed - I can then synchronize with TFS version
control and pick up an edit-change on the pom.
I propose an additional option 'forceWritable' to be added so versions plugin
would ensure pom.xml is writable before modifying it - this would solve the
issue for TFS (probably for clearcase too).
Please find enclosed 'forceWritable.patch' that adds 'forceWritable' option to
all version update goals (revert goal does not have this option since pom.xml
should already be writable when this goal is used; please do correct me if I'm
wrong).
Example usage after applying the patch is: mvn versions:set
-DnewVersion=1.0.1-SNAPSHOT -DforceWritable
was (Author: mzagar):
We use TFS and have the same issue since TFS stores files as read-only
until they are explicity checked out.
This prevents me to use versions plugin efficiently since the process of
checking out all the poms on a multimodule project to remove read-only flag and
then modify them can be tiring.
In my case it would be enough to clear read-only flag on pom.xml and make it
writable before it is processed - I can then synchronize with TFS version
control and pick up an edit-change on the pom.
I propose an additional option 'forceWritable' to be added so versions plugin
would ensure pom.xml is writable before modifying it - this would solve the
issue for TFS (probably for clearcase too).
Please find enclosed a patch that adds 'forceWritable' to all version update
goals (revert goal does not have this option since pom.xml should already be
writable when this goal is used; please do correct me if I'm wrong).
> The project's SCM should be used to make sure files are writable
> ----------------------------------------------------------------
>
> Key: MVERSIONS-68
> URL: http://jira.codehaus.org/browse/MVERSIONS-68
> Project: Maven 2.x Versions Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Peter Hayes
> Attachments: forceWritable.patch
>
>
> We use clearcase and the versions plugin doesn't seem to interact with the
> SCM when updating pom files. It would be useful if this plugin had an option
> to interact with the SCM to make the pom's writable prior to updating and
> optionally check back in files once editing has been completed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
