[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] joe freeman updated JBIDE-8331: ------------------------------- Affects Version/s: 3.2.0.M2 Description: The JBPM 3 file naming change mentioned in https://issues.jboss.org/browse/JBIDE-8330 combined with the SCM breakage from https://issues.jboss.org/browse/JBIDE-7732 breaks Eclipse SCM plugins (Perforce) that require file checkouts when editing files. The new naming convention creates a hidden file that can't be seen by the user. The old pre JBIDE-7732 behavior let the SCM system automatically check out and unlock files when opening for edit in Eclipse. Then the problem reported in JBIDE-7732 bypassed the SCM/file hooks so that folks were REQUIRED to manually check out all 3 JBPM files for a process definition. Now the new JBIDE-8330 behavior in 3.2.0 (maybe 3.1.0?) editor hides the gpd files from view which means it is no longer possible to check out in Eclipse. The two changes in behavior make it very difficult to use JBpm 3.2.0 in Eclipse for new JBPM 3 process definitions under version control where file check outs are required. It looks like this change was introduced in 3.2.0M2 per http://docs.jboss.org/tools/whatsnew/jbpm/jbpm-news-3.2.0.M2.html. There filtering of file types should be a preferences setting. Magic, invisible, files can be confusing to developers. was: The JBPM 3 file naming change mentioned in https://issues.jboss.org/browse/JBIDE-8330 combined with the SCM breakage from https://issues.jboss.org/browse/JBIDE-7732 breaks Eclipse SCM plugins (Perforce) that require file checkouts when editing files. The new naming convention creates a hidden file that can't be seen by the user. The old pre JBIDE-7732 behavior let the SCM system automatically check out and unlock files when opening for edit in Eclipse. Then the problem reported in JBIDE-7732 bypassed the SCM/file hooks so that folks were REQUIRED to manually check out all 3 JBPM files for a process definition. Now the new JBIDE-8330 behavior in 3.2.0 (maybe 3.1.0?) editor hides the gpd files from view which means it is no longer possible to check out in Eclipse. The two changes in behavior make it very difficult to use JBpm 3.2.0 in Eclipse for new JBPM 3 process definitions under version control where file check outs are required. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick updated JBIDE-8331: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8331: -------------------------------------------- okey so i've looked at the various linked issues and I simply can't see what API it is you want us to use that will make your SCM happy (Perforce seem to be the only one having this issue). If you can tell me what API it is you mean is what is needed to call to avoid having the problem that JBIDE-3915 tried to fix ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8331: -------------------------------------------- 1) Perforce seem to be the *only* one having these problems and there is no way (afaik) for us to call out to team code to "enable write". 2) I agree with that we should not toggle any read/write flags - the editor should simply just refuse to save in this case. 3) you can go to the package explorer, click the view menu and choose Filters - here you can uncheck the ".* resources" and they will show up. 4) #3 is a workaround; but it should allow you to work. 5) Not sure what we can do to fix this beyond maybe also allow the .file to be named without the dot and the editor would use that instead. Would that work for you ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] joe freeman commented on JBIDE-8331: ------------------------------------ I did more experimentation in JBIDE-7732 added a comment that shows the three files SCM status varies based on the scenario and that the jpg file is never checked out automatically. Manual check out of all three files always works which is why I'm asking to not hide the file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBIDE-8331: ------------------------------------------ Doesn't seem to be any movement on this one... Any more word from Perforce? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8331: --------------------------------------- Fix Version/s: 3.2.x LATER (was: 3.2.1.CR1) No word or info from user/perforce so moving this off the fix list. If you get info let us know. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8331?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick updated JBIDE-8331: ------------------------------------- Fix Version/s: (was: 3.2.x) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira