October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-1646) jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload" in JBDS 4

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-1646?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBDS-1646: ----------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 780614|https://bugzilla.redhat.com/show_bug.cgi?id=780614] from VERIFIED to CLOSED > jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload" in JBDS 4 > -------------------------------------------------------------------------------------------- > > Key: JBDS-1646 > URL: https://issues.jboss.org/browse/JBDS-1646 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: jbpm > Affects Versions: 4.0.1.GA > Reporter: Brian Fitzpatrick > Assignee: Koen Aers > Priority: Critical > Fix For: 4.1.0.CR1, 5.0.0.M2 > > Attachments: JBDS-1646.patch > > > See SOA-3052, but this seems to be the same issue we've fought for several releases as far as the URL goes between JBoss Tools & JBDS. > Koen mentioned he thought Snjezana might know where the code is in JBDS to set the correct preference. Denis might also know. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1645) JBDS 4 - jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-1645?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBDS-1645: ----------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 780614|https://bugzilla.redhat.com/show_bug.cgi?id=780614] from VERIFIED to CLOSED > JBDS 4 - jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload" > ---------------------------------------------------------------------------------------------- > > Key: JBDS-1645 > URL: https://issues.jboss.org/browse/JBDS-1645 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: jbpm > Environment: Version: 4.0.0.GA > Build id: v20110216-1930-H239-GA > Build date: 20110216-1930 > Reporter: Len DiMaggio > Assignee: Koen Aers > Priority: Critical > Fix For: 4.1.0.CR1 > > > Related to https://issues.jboss.org/browse/SOA-2937 > The enterprise is using "/gpd-deployer/upload" and the community is using "/jbpm-console/upload". > For JBDS, we should have the default value be "/gpd-deployer/upload" - as this is what the SOA Platform requires. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12285) Enable and Fix Tests for DRL Editor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12285?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12285: ------------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 833329|https://bugzilla.redhat.com/show_bug.cgi?id=833329] from VERIFIED to CLOSED > Enable and Fix Tests for DRL Editor > ----------------------------------- > > Key: JBIDE-12285 > URL: https://issues.jboss.org/browse/JBIDE-12285 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools > Affects Versions: 3.3.0.Beta3-SOA > Reporter: Alexandre Porcelli > Assignee: Kris Verlaenen > Fix For: 3.3.0.CR2-SOA > > > Due an unknown reason, most tests of DRL editor were disabled (@Ignore). If enabled most of them fails (+50 fails). > This issue is also relate to JBIDE-12210 and JBIDE-12212 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12210) Wrong/No completion for the second field constraint in Drools Rule Editor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12210?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12210: ------------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 833323|https://bugzilla.redhat.com/show_bug.cgi?id=833323] from VERIFIED to CLOSED > Wrong/No completion for the second field constraint in Drools Rule Editor > ------------------------------------------------------------------------- > > Key: JBIDE-12210 > URL: https://issues.jboss.org/browse/JBIDE-12210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools > Affects Versions: 3.3.0.Beta3-SOA > Environment: JBDS500beta2 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta3.soa... > Reporter: Toshiya Kobayashi > Assignee: Kris Verlaenen > Fix For: 3.3.0.CR2-SOA > > Attachments: DroolsEx01_code_completion.zip > > > A. Rule Editor doesn't raise a completion list for the second field constraint. > {code:java} > rule "No completion for second constraint" > when > Person( name != "John", ) > then > > end > {code} > Click ctrl+space after ',' -> no popup > B. Rule Editor raises a wrong completion list, which indicates fields of a preceded fact, for the second field constraint. > {code:java} > rule "wrong completion for second constraint in case it has preceded fact" > when > Cheese( type == "cream" ) > Person( name != "John", ) > then > > end > {code} > Click ctrl+space after ',' -> the popup completion list includes Cheese's fields like 'type', not Person's fields. > In the attached example project, Sample01.drl is for A. Sample02.drl is for B. (please ignore Sample03/04) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12212) Wrong/No completion for bind variable in Drools Rule Editor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12212?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12212: ------------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 833329|https://bugzilla.redhat.com/show_bug.cgi?id=833329] from VERIFIED to CLOSED > Wrong/No completion for bind variable in Drools Rule Editor > ----------------------------------------------------------- > > Key: JBIDE-12212 > URL: https://issues.jboss.org/browse/JBIDE-12212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools > Affects Versions: 3.3.0.Beta3-SOA > Environment: JBDS500beta2 > http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta3.soa... > Reporter: Toshiya Kobayashi > Assignee: Kris Verlaenen > Fix For: 3.3.0.CR2-SOA > > Attachments: DroolsEx01_code_completion.zip > > > A. Rule Editor raises a wrong completion list, which includes drools keywords, for a bind variable in LHS. > {code:java} > rule "Wrong completion for bind valiable in LHS" > when > $p : Person( name != "John") > eval($p.) > then > > end > {code} > Click ctrl+space after '$p.' -> the popup completion list includes 'and' 'eval' ... > B. Rule Editor doesn't raise a completion list for a bind variable in RHS. > {code:java} > rule "No completion for bind valiable in RHS" > when > $p : Person( name != "John") > then > $p. > end > {code} > Click ctrl+space after '$p.' -> no popup > In the attached example project, Sample03.drl is for A. Sample04.drl is for B. (please ignore Sample01/02) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12285) Enable and Fix Tests for DRL Editor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12285?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12285: ------------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 833323|https://bugzilla.redhat.com/show_bug.cgi?id=833323] from VERIFIED to CLOSED > Enable and Fix Tests for DRL Editor > ----------------------------------- > > Key: JBIDE-12285 > URL: https://issues.jboss.org/browse/JBIDE-12285 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools > Affects Versions: 3.3.0.Beta3-SOA > Reporter: Alexandre Porcelli > Assignee: Kris Verlaenen > Fix For: 3.3.0.CR2-SOA > > > Due an unknown reason, most tests of DRL editor were disabled (@Ignore). If enabled most of them fails (+50 fails). > This issue is also relate to JBIDE-12210 and JBIDE-12212 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10183) BPEL - cannot change the fixed value generated by variable initializer.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10183?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-10183: ------------------------------------------------- Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 781103|https://bugzilla.redhat.com/show_bug.cgi?id=781103] from VERIFIED to CLOSED > BPEL - cannot change the fixed value generated by variable initializer. > ----------------------------------------------------------------------- > > Key: JBIDE-10183 > URL: https://issues.jboss.org/browse/JBIDE-10183 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.2.2.Final > Environment: JBT version 3.2.2.CR4 inside JBDS 4.1.1.GA > Reporter: Marek Baluch > Assignee: Robert (Bob) Brodt > Fix For: 3.3.0.M5 > > Attachments: Screenshot.png > > > The fixed value generated by BPEL variable initializer cannot be changed using the UI. I attempt to change the assigned value but saving the changes does not have any effect. To make the save work it's required to close/open the .bpel process document. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18640) For JBIDE 4.2.0.Final: Prepare for Final/GA release [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18640?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18640: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.2.0.Final: Prepare for Final/GA release [JavaEE] > ------------------------------------------------------------ > > Key: JBIDE-18640 > URL: https://issues.jboss.org/browse/JBIDE-18640 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [JavaEE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18638) For JBIDE 4.2.0.Final: Prepare for Final/GA release [Base]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18638?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18638: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.2.0.Final: Prepare for Final/GA release [Base] > ---------------------------------------------------------- > > Key: JBIDE-18638 > URL: https://issues.jboss.org/browse/JBIDE-18638 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [Base]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18632) For JBIDE 4.2.0.Final: Prepare for Final/GA release [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18632?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18632: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.2.0.Final: Prepare for Final/GA release [JST] > --------------------------------------------------------- > > Key: JBIDE-18632 > URL: https://issues.jboss.org/browse/JBIDE-18632 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [JST]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014