Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-8476

JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)

    XMLWordPrintable

Details

    • Hide

      Setup a couple projects in Eclipse where all the files are read only under Eclipse SCM control. Rename a method (alt-shift-r). You will get a lot of "Cannot change read-only file..." messages even on files that should be unaffected.

      Remove the Rich Faces plugin and try again.

      Show
      Setup a couple projects in Eclipse where all the files are read only under Eclipse SCM control. Rename a method (alt-shift-r). You will get a lot of "Cannot change read-only file..." messages even on files that should be unaffected. Remove the Rich Faces plugin and try again.

    Description

      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.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-8491 2 CDI tests fail after changes made for JBIDE-8476

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-8521 Compile failed in org/jboss/tools/cdi/internal/core/refactoring/CDIRenameProcessor.java

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              dazarov_jira Daniel Azarov (Inactive)
              joe_jboss joe freeman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: