[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-5595) Selections on deployment screen get undone after saving project

[Koen Aers (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koen Aers resolved JBIDE-5595.
------------------------------

    Resolution: Won't Fix


This is actually not a very easy problem to solve, as there is no location where these dependencies can be stored (i.e. deployment descriptor). Moreover, the deployment page is only there to provide a convenient way for deployment for demo purposes. In no way it is meant to be used for repeated deployment in a production or test environment. The preferred way for deploying process definitions along with their different dependencies is with ant scripts. The ant deploy target will thus serve as a deployment descriptor. This guarantees repeatability of the deployment and testability of the deployed artifacts.

> Selections on deployment screen get undone after saving project
> ---------------------------------------------------------------
>
>                 Key: JBIDE-5595
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5595
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jbpm
>         Environment: JBDS 3.0 M4
>            Reporter: Aaron Pestel
>            Assignee: Koen Aers
>             Fix For: 3.1.0.CR2
>
>
> 1.)  Create a new jBPM project.
> 2.)  Save it
> 3.)  Click on the jBPM editor "Deployment" tab
> 4.)  select the "src/java/main" check box in the Java Class and Resources area of the panel
> 5.)  select the "Source" tab
> 6.)  add a space anywhere in the process file (just to trigger it needing a save)
> 7.)  click back on the "Deployment" tab
> 8.)  click the "Save" toolbar icon
> 9.)  watch your "src/java/main" checkbox get unchecked.
> The same thing happens for the "Files and Folders" section of the panel.  Clicking "save" will revert to the default of selecting everything in that panel.
> It might seem like this is a minor bug - and technically it probably is.  But, it's a major pain when you actually have jBPM Java Actions in your process and you have to remember to select that check box every time you deploy after having saved the project (basically every time you would ever deploy).  If you don't, you won't get an error - until you run the process and get a ClassNotFound error because your class was was not actually deployed in the process archive.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira