Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution:
Out of Date
-
Affects Version/s: 3.2.0.M2, 3.2.0.CR1
-
Fix Version/s: LATER
-
Component/s: jbpm
-
Labels:None
-
Steps to Reproduce:
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.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
About 1) if you can get info from Perforce on how we best handle this to be "nice" to their "checkout before write"-workflow that would be great. I'm actually very curious since I would like our other plugins to be "nice" too if possible.
Max Rydahl Andersen
added a comment - About 1) if you can get info from Perforce on how we best handle this to be "nice" to their "checkout before write"-workflow that would be great. I'm actually very curious since I would like our other plugins to be "nice" too if possible. Doesn't seem to be any movement on this one... Any more word from Perforce?
Brian Fitzpatrick
added a comment - Doesn't seem to be any movement on this one... Any more word from Perforce? No word or info from user/perforce so moving this off the fix list. If you get info let us know.
Max Rydahl Andersen
added a comment - No word or info from user/perforce so moving this off the fix list. If you get info let us know. 
How do you guys handle eclipse's .settings folders and files ?
And how about .svnignore, .gitignore etc. ?