[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8331) New JBPM 3 process definition file naming and Eclipse view filtering breaks SCM

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-8331:
--------------------------------------------

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.

> 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: http://www.atlassian.com/software/jira