create packaging
----------------
Key: JBPM-1869
URL: https://jira.jboss.org/jira/browse/JBPM-1869
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha1
Create packaging for jbpm 4.
For this first alpha release of jbpm i'm not yet sure whether I'll manage to build an installer. Plan B is to create a simpler zip file for this release.
--
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
generate db scripts
-------------------
Key: JBPM-1873
URL: https://jira.jboss.org/jira/browse/JBPM-1873
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha1
Add an artifact to pvm that contains all the DB schema DDL scripts.
Potentially, evaluate if it's necessary to create a separate db module that contains these DB schema DDL scripts as source files. I think it is sufficient if we generate those and have them as an artifact in the repository.
--
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
expose clock functionality in test base classes
-----------------------------------------------
Key: JBPM-1857
URL: https://jira.jboss.org/jira/browse/JBPM-1857
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha1
--
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
define strategy on task and execution variables
-----------------------------------------------
Key: JBPM-1865
URL: https://jira.jboss.org/jira/browse/JBPM-1865
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha1
--
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
expose task lists through task service api
------------------------------------------
Key: JBPM-1859
URL: https://jira.jboss.org/jira/browse/JBPM-1859
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha1
task lists should be exposed by pages, preventing scalability problems.
the group task lists should be based on contacting the identiy component through our identity component SPI
--
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
[ https://jira.jboss.org/jira/browse/JBPM-1227?page=com.atlassian.jira.plug... ]
Tom Baeyens resolved JBPM-1227.
-------------------------------
Resolution: Done
deleted, replaced by load and functional tests
> fix tests HibernateJobDbSessionTest and JobExecutorTimerSessionTest
> -------------------------------------------------------------------
>
> Key: JBPM-1227
> URL: https://jira.jboss.org/jira/browse/JBPM-1227
> Project: JBoss jBPM
> Issue Type: Task
> Components: PVM
> Reporter: Tom Baeyens
> Assignee: Tom Baeyens
> Fix For: jBPM 4.0.0 Alpha1
>
>
> I've added some comments as TODO's in the code. The complete code is commented.
> First fix test HibernateJobDbSessionTest and then and JobExecutorTimerSessionTest and the former contains more instructions/comments.
--
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
[ https://jira.jboss.org/jira/browse/JBPM-1066?page=com.atlassian.jira.plug... ]
Daniel Woo commented on JBPM-1066:
----------------------------------
Yes, I also encounter the same problem, mail node and mail action can only specify 'actors' or 'to', that means I have to change the process definition each time a new user need to be notified or an existing user resigned.
> equivalent of pooled-actors group functionality in mailnodes
> ------------------------------------------------------------
>
> Key: JBPM-1066
> URL: https://jira.jboss.org/jira/browse/JBPM-1066
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Affects Versions: jBPM 3.2.1, jBPM 3.2.2
> Environment: any
> Reporter: Ross McDonald
> Priority: Minor
>
> It would be nice to be able to specify a group to mail to within mail nodes, to save having to put semicolon separated actors in. This would enable the database to control who is going to be emailed, and avoid the need to keep updating processes etc
--
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
Ensure backward compatibility of the API
----------------------------------------
Key: JBPM-1919
URL: https://jira.jboss.org/jira/browse/JBPM-1919
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
Assignee: Bernd Ruecker
Priority: Blocker
Fix For: jBPM 3.3.1 GA
Obvious incompatibilities are in
[code]
BatchSignalCommand
ChangeProcessInstanceVersionCommand
DeleteProcessdefinitionCommand
HibernateHelper
[/code]
--
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