[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8476) JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)

[joe freeman (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584957#comment-12584957 ] 

joe freeman commented on JBIDE-8476:
------------------------------------

I pulled down the latest from the nightly builds http://download.jboss.org/jbosstools/updates/nightly/trunk.  jbpm and others are showing with a date of v20110227-2131-xxx-Alpha1 but "JBoss Tools RichFaces" is coming in with v20110124-1345-H70-CR1.  That implies that the rich faces change isn't making it into the nightly builds and out to the update site

> JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-8476
>                 URL: https://issues.jboss.org/browse/JBIDE-8476
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsp/jsf/xml source editing
>    Affects Versions: 3.2.0.CR1
>         Environment: 3.2.0 GA Rich Faces Editor Mac and Windows Eclipse 3.6  Perforce (or possibly other READ/ONLY based SCM)
>            Reporter: joe freeman
>            Assignee: Daniel Azarov
>            Priority: Critical
>              Labels: richfaces
>             Fix For: 3.2.1, 3.3.0.M1
>
>
> We have a large project that uses Perforce as SCM.  Perforce leaves files read/only until they have been modified at which point they are checked out and made writable.  
> Eclipse refactoring modifies files and automatically engages the SCM Eclipse plugins on changes to optionally check the files out. In the case of Perforce, this makes the files writable on modification which allows changes to be saved. This works fine under Eclipse 3.5 with Jboss Tools.  
> This is broken under Eclipse 3.6, Jboss tools 3.2 when the RichFaces editor is installed and a developer attempts to rename a method using "refactor Method name".  You get a set of error messages where it looks like the refactoring is trying to change read-only files.  Many of the files listed are not changed by the refactoring. It's almost like the Rich Faces editor/refactor hooks is stat'ing or touching the files maybe without changing.  Removing the RichFaces editor stops the problem for occurring.
> No work around exists.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira