[JBoss JIRA] Closed: (JBPM-127) create packaging strategy
by Koen Aers (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-127?page=all ]
Koen Aers closed JBPM-127.
--------------------------
Resolution: Done
This is also done through the use of the deployment page in the editor. GPD-9 is related.
> create packaging strategy
> -------------------------
>
> Key: JBPM-127
> URL: http://jira.jboss.com/jira/browse/JBPM-127
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Graphical Process Designer
> Reporter: Tom Baeyens
> Assigned To: Koen Aers
>
> add links from the graphical information to the process definition, forms and classes so that a .par file can be generated.
> The data should be editable in the graphical process designer and should correspond to the data for the ant zip task. ideally this information should be stored as an ant-zip-task in the *.gpd.xml
> Packaging can then be based on this and zip task. A ant build file is generated from the ant zip task in some temporary location. then executed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBPM-202) refactor naming strategy
by Koen Aers (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-202?page=all ]
Koen Aers closed JBPM-202.
--------------------------
Resolution: Done
Replaced by GPD-20
> refactor naming strategy
> ------------------------
>
> Key: JBPM-202
> URL: http://jira.jboss.com/jira/browse/JBPM-202
> Project: JBoss jBPM
> Issue Type: Task
> Components: Graphical Process Designer
> Reporter: Koen Aers
> Assigned To: Koen Aers
>
> 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type.
> 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though.
> 3) use the following naming strategy for end states: {end, end2, end3, end4, ...}
> 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name.
> 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBPM-755) streamline designer build
by Tom Baeyens (JIRA)
streamline designer build
-------------------------
Key: JBPM-755
URL: http://jira.jboss.com/jira/browse/JBPM-755
Project: JBoss jBPM
Issue Type: Task
Components: Graphical Process Designer
Reporter: Tom Baeyens
Assigned To: Koen Aers
Priority: Critical
1) Remove usage of jbpm.version.
* The docs should not be included directly in the designer plugin. Instead, in the help docs, a reference should be published to the docs of the configured runtimes.
* The jbpm version constant should be removed cause it's not used any more.
When fixing this, make sure to do a search for jbpm.version.
2) Rename jbpm.gpd.version to module.version so that it is in sync with all other jbpm subprojects. Make sure that the used definition is located in the version.properties file and that the property definition in the build.xml is removed.
3) Remove all CVS checkout stuff. Have the build fail in case one of the submodules is not present. No cvs checkout should be done in case a module is missing. Later we'll define a cvs checkout script in the overall build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months