]
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 ?
New JBPM 3 process definition file naming and Eclipse view filtering
breaks SCM
-------------------------------------------------------------------------------
Key: JBIDE-8331
URL:
https://issues.jboss.org/browse/JBIDE-8331
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.M2, 3.2.0.CR1
Reporter: joe freeman
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: