February 2012 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1771) JBDS50_0450: [COMMIT] (PM) Document Bit Delivery Channels

by mark yarborough (JIRA)

JBDS50_0450: [COMMIT] (PM) Document Bit Delivery Channels --------------------------------------------------------- Key: JBDS-1771 URL: https://issues.jboss.org/browse/JBDS-1771 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
14
0 / 0

[JBoss JIRA] (JBDS-2012) verify what version(s) of jBPM should be in JBoss Tools and JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2012: -------------------------------- Summary: verify what version(s) of jBPM should be in JBoss Tools and JBDS Key: JBDS-2012 URL: https://issues.jboss.org/browse/JBDS-2012 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, jBPM Affects Versions: 5.0.0.SOA, 5.0.0.Beta1 Reporter: Nick Boldt Assignee: Kris Verlaenen Fix For: 5.0.0.Beta1 Noticed today that there are jbpm features in the JBT SOA Tooling site which are not in the JBDS SOA Tooling site. Attached is a screenshot comparing these two site.xml files. Please verify what's there is correct and if it's not, add missing features (ore removed unwanted ones) as required. -- 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

13 years, 12 months

3
19
0 / 0

[JBoss JIRA] Created: (JBIDE-9257) Runtime detectors for SOA are missing in updatesite

by Libor Zoubek (JIRA)

Runtime detectors for SOA are missing in updatesite --------------------------------------------------- Key: JBIDE-9257 URL: https://issues.jboss.org/browse/JBIDE-9257 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite, drools, jbpm Affects Versions: 3.3.0.M2 Reporter: Libor Zoubek Assignee: Douglas Palmer Priority: Critical Fix For: 3.3.0.M3 I just installed http://download.jboss.org/jbosstools/builds/development/3.3.0.M2.soa-tool... (H6) on top of indigo with http://download.jboss.org/jbosstools/builds/development/3.3.0.M2/ (H6), Detection of runtimes does not work, for SOA technologies like drools, jBPM (and others?) AFAIK this functionality is provided by several plugins (1 per technology) which are missing. Without these plugins SOA-P builds are not fully recognized by Runtime Detection Preference page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

7
7
0 / 0

[JBoss JIRA] (JBDS-1906) Cannot run Drools project created in JBDS 5.0.0.M4 - java.lang.ClassNotFoundException: org.jbpm.bpmn2.BPMN2ProcessProviderImpl

by Len DiMaggio (Created) (JIRA)

Cannot run Drools project created in JBDS 5.0.0.M4 - java.lang.ClassNotFoundException: org.jbpm.bpmn2.BPMN2ProcessProviderImpl ------------------------------------------------------------------------------------------------------------------------------ Key: JBDS-1906 URL: https://issues.jboss.org/browse/JBDS-1906 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 5.0.0.M4 Environment: SOA-P 5.2.0.ER5 Version: 5.0.0.M4 Build id: v20111025-0135-H35-M4 Build date: 20111025-0135 Reporter: Len DiMaggio Fix For: 5.0.0.Beta1 To recreate: New->Project->Drools Project When running the ProcessTest class - this exception is raised: java.lang.IllegalArgumentException: Unable to instantiate service for Class 'org.drools.compiler.BPMN2ProcessProvider' at org.drools.util.ServiceRegistryImpl.get(ServiceRegistryImpl.java:161) at org.drools.compiler.BPMN2ProcessFactory.loadProvider(BPMN2ProcessFactory.java:29) at org.drools.compiler.BPMN2ProcessFactory.getBPMN2ProcessProvider(BPMN2ProcessFactory.java:21) at org.drools.compiler.BPMN2ProcessFactory.configurePackageBuilder(BPMN2ProcessFactory.java:12) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:566) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:35) at com.sample.ProcessTest.readKnowledgeBase(ProcessTest.java:33) at com.sample.ProcessTest.main(ProcessTest.java:20) Caused by: java.lang.IllegalArgumentException: Unable to instantiate 'org.jbpm.bpmn2.BPMN2ProcessProviderImpl' at org.drools.util.ServiceRegistryImpl$ReflectionInstantiator.newInstance(ServiceRegistryImpl.java:210) at org.drools.util.ServiceRegistryImpl$ReflectionInstantiator.call(ServiceRegistryImpl.java:202) at org.drools.util.ServiceRegistryImpl.get(ServiceRegistryImpl.java:159) ... 7 more Caused by: java.lang.ClassNotFoundException: org.jbpm.bpmn2.BPMN2ProcessProviderImpl at java.net.URLClassLoader$1.run(URLClassLoader.java:217) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at org.drools.util.ServiceRegistryImpl$ReflectionInstantiator.newInstance(ServiceRegistryImpl.java:207) ... 9 more -- 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

13 years, 12 months

7
9
0 / 0

[JBoss JIRA] (JBIDE-10715) "Path" Environment Variable in Launch Configuration is overridden with the text "native" by default

by Daniel Atallah (JIRA)

Daniel Atallah created JBIDE-10715: -------------------------------------- Summary: "Path" Environment Variable in Launch Configuration is overridden with the text "native" by default Key: JBIDE-10715 URL: https://issues.jboss.org/browse/JBIDE-10715 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Windows 7 / Eclipse Indigo SR1 / JBoss 4.2.3 Reporter: Daniel Atallah Assignee: Rob Stryker When a new Launch configuration is created for a JBoss 4.2 Runtime server, the "Environment" tab contains an initial entry for the "Path" variable with a value of "native". This causes the Path of the launched process to be overridden and subsequently not work correctly if you depend on the System Path for anything. -- 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

13 years, 12 months

4
12
0 / 0

[JBoss JIRA] (JBDS-2046) Determine categories and feature groups in JBT/JBDS SOA Tooling's Central; determine categories in JBT/JBDS SOA Tooling's aggregate site

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2046: -------------------------------- Summary: Determine categories and feature groups in JBT/JBDS SOA Tooling's Central; determine categories in JBT/JBDS SOA Tooling's aggregate site Key: JBDS-2046 URL: https://issues.jboss.org/browse/JBDS-2046 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: Build, central, updatesite Affects Versions: 5.0.0.Beta1 Environment: Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 5.0.0.Beta1 Attachments: screenshot0.png Determine categories and feature groups in JBT/JBDS SOA Tooling's Central; determine categories in JBT/JBDS SOA Tooling's aggregate site -- 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

13 years, 12 months

9
52
0 / 0

[JBoss JIRA] (JBIDE-10576) Provide linking capability for all field editors in forms of JBoss Tools XML Editor

by Viacheslav Kabanovich (Created) (JIRA)

Provide linking capability for all field editors in forms of JBoss Tools XML Editor ----------------------------------------------------------------------------------- Key: JBIDE-10576 URL: https://issues.jboss.org/browse/JBIDE-10576 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: common/jst/core Affects Versions: 3.3.0.M5 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 Now the linking capability is implemented only in text+button field editors. In some cases a drop-down field editor is used for attributes referencing other objects that may be linked. -- 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

13 years, 12 months

6
9
0 / 0

[JBoss JIRA] (JBDS-1983) JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring, FindBugs, PMD

by Nick Boldt (Created) (JIRA)

JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring, FindBugs, PMD -------------------------------------------------------------------------------------------------------- Key: JBDS-1983 URL: https://issues.jboss.org/browse/JBDS-1983 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome Affects Versions: 5.0.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.Beta2 We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a new Welcome screen, leading to this issue: !https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png! However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel also have this failing. Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead of per-plugin, or get it fixed upstream. -- 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

13 years, 12 months

9
39
0 / 0

[JBoss JIRA] Created: (JBDS-1620) CLONE - Enable dropin folder reconciling by default for JBDS product

by Denis Golovin (JIRA)

CLONE - Enable dropin folder reconciling by default for JBDS product -------------------------------------------------------------------- Key: JBDS-1620 URL: https://issues.jboss.org/browse/JBDS-1620 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.1.0.GA Now to get that supported several additions steps should be done: To activate dropins reconciling you need to do the following: - open studio/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - find the line org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,false and change it to org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,true - create the studio/dropins directory and add plugins as is usual - start JBDS with the -clean option at least once To eliminate this steps plugin org.eclipse.equinox.p2.reconciler.dropins should be marked as auto started in jbds-all.product definition which is used to build JBDS product -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
11
0 / 0

[JBoss JIRA] (JBIDE-10696) "error" for "non-error" conditions in openshift

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10696: ------------------------------------------- Summary: "error" for "non-error" conditions in openshift Key: JBIDE-10696 URL: https://issues.jboss.org/browse/JBIDE-10696 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 not sure if this is databinding limitations or our usage of databinding but i.e. when unselecting "Create new project" in openshift wizard I instantly get an "error icon/message" saying "select an existing project to use with OpenShift" - this feels rather "abrupt" since the user haven't actually done anything out of the ordinary, he is just filling in the form. i.e. in eclipse JDT it will just state "Enter a location for the project" with no error icon and finish disabled. I believe Eclipse UI guidelines says the same "5.5 Validate the wizard data in tab order. Display a prompt when information is absent, and an error when information is invalid." http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards -- 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

13 years, 12 months

4
9
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 February 2012