[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-12345: -------------------------------------------- Bugzilla Update: Perform -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12345: ------------------------------------------------- Andrej Podhradsky <apodhrad(a)redhat.com&gt; made a comment on [bug 780434|https://bugzilla.redhat.com/show_bug.cgi?id=780434] Tested on JBDS 5.0.1.GA-H232 with SOA Tooling 5.0.0.GA-H18: Not working for jBPM3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12345: ------------------------------------------------- Len DiMaggio <ldimaggi(a)redhat.com&gt; made a comment on [bug 780434|https://bugzilla.redhat.com/show_bug.cgi?id=780434] I think that the problem that Andrej is seeing is that when the user creates a new jBPM3 project, he is not moved into the jBPM perspective. Instead, the user remains in the same perspective from which he created the jBPM project. This is a different bug from the original bug for which this bugzilla was logged. Andrej - can you log a new bugzilla for this new issue? It's not a blocker for the release of the tooling or for SOA-P 5.3, but it could result in some user confusion as creating other projects (e.g., BPEL) do give the user the option of moving to that new project's perspective. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-12345: -------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780434 (was: https://bugzilla.redhat.com/show_bug.cgi?id=780434) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-12345: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=841495 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-12345: --------------------------------- Assignee: Len DiMaggio (was: Koen Aers) Hey Len, I don't know what to do with this. Is it solved? If yes, the issue can be closed right? If not, do you know who this should be assigned to as I'm not really working on jBPM anymore? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-12345: ------------------------------------------- Tested version: JBDS 5.0.1.GA + SOA Tooling 5.0.1.GA Expected behaviour: after creating a new jBPM3 project eclipse should give the user an option to go into jBPM jPDL perspective. Actual behavior: after creating a new jBPM3 project nothing happens (only the project is created) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-12345?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12345: ------------------------------------------------- Len DiMaggio <ldimaggi(a)redhat.com&gt; made a comment on [bug 881131|https://bugzilla.redhat.com/show_bug.cgi?id=881131] Description of problem: https://issues.jboss.org/browse/JBIDE-12345 Creating a new jBPM3 project does not open the jBPM perspective Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira