BPEL Editor does not observe "Layout Flow children automatically" preference at startup
---------------------------------------------------------------------------------------
Key: JBIDE-6032
URL: https://jira.jboss.org/jira/browse/JBIDE-6032
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Affects Versions: 3.1.0.CR2
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Priority: Minor
Fix For: 3.2.next
Imported BPEL processes, or processes that were edited in the BPEL "Source" view will not automatically lay out Flow activity contents even if the "Auto Layout" preference is set. Toggling the auto layout preference does not change the editor's "dirty" bit (and this is correct behaviour) so simply toggling this flag off and back on does not force an auto layout.
--
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
Need a build of "common" component & "common tests" using Athena + Hudson
-------------------------------------------------------------------------
Key: JBIDE-5172
URL: https://jira.jboss.org/jira/browse/JBIDE-5172
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
Assignee: Nick Boldt
create an Athena builder for "JBT common" + bundle tests into resulting update site; this will allow Hibernate and BPEL builders to be able to run their tests.
--
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
Hibernate Tools SDK & Athena Builder
------------------------------------
Key: JBIDE-4959
URL: https://jira.jboss.org/jira/browse/JBIDE-4959
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.1.0.M4
create sdk feature
create athena builder
hook sdk feature into uberbuilder
add sdk feature to site.xml (x2)
verify source feature and sdk feature on update sites
--
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
Hibernate mapping metadata portability validator
------------------------------------------------
Key: JBIDE-5164
URL: https://jira.jboss.org/jira/browse/JBIDE-5164
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
This validator post warn/error markers to make Domain Meta model developer aware of database portability problems in application. Example is using real class in generator class field instead of placeholder. All cases like this should be identified.
--
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
Hibernate Configurations view doesn't reflect the changes in mappings sources
-----------------------------------------------------------------------------
Key: JBIDE-612
URL: http://jira.jboss.com/jira/browse/JBIDE-612
Project: JBoss Tools
Issue Type: Bug
Components: Hibernate
Reporter: Denis Golovin
Assigned To: Denis Golovin
--
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
Highlight matching brackets in HQL Editor
-----------------------------------------
Key: JBIDE-5805
URL: https://jira.jboss.org/jira/browse/JBIDE-5805
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Reporter: Krasimir Goutcev
Why don't we have Highlight matching brackets?
--
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
Bahaviour of "Make Deployable" and "Make Undeployable" is not consistent
------------------------------------------------------------------------
Key: JBIDE-5865
URL: https://jira.jboss.org/jira/browse/JBIDE-5865
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
When "Make Deployable" is applied to a resource, and a server is running, it gets immediatelly deployed.
When "Make Undeployable" is applied to a resource on running server, it is correctly removed from a list of resources available for deployment, but it is not undeployed.
Make Deployable/Undeployable should:
1) not deploy/undeploy resource immediately (preferably)
2) or both deploy/undeploy immediately.
--
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
Process is not removed from ODE deployment editor model if BPEL process file is deleted from project
----------------------------------------------------------------------------------------------------
Key: JBIDE-6230
URL: https://jira.jboss.org/jira/browse/JBIDE-6230
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Fix For: 3.2.next
Like the title says: if a bpel file is deleted from the workspace, the process entry is never removed from the ODE deployment model.
This is part of a bigger problem having to do with refactoring: see https://jira.jboss.org/jira/browse/JBIDE-6018 and https://jira.jboss.org/jira/browse/JBIDE-5027
but at the very least, the deployment model should be kept in sync if bpel files are created or deleted.
Also, if the name of the bpel process is changed, the deployment editor assumes it is a new process and adds it to the model. This is not tragic, but the user must then re-select the inbound and outbound ports.
--
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