November 2011 - jbosstools-issues

[JBoss JIRA] (JBIDE-10034) When you try to create the 6th application, error says "could not configure", not mentioning that 5 apps is the maximum

by Andre Dietisheim (Created) (JIRA)

When you try to create the 6th application, error says "could not configure", not mentioning that 5 apps is the maximum ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10034 URL: https://issues.jboss.org/browse/JBIDE-10034 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Attachments: cannot-create-6th-app.png In OpenShift Express you can actually only create 5 applications. In the tooling, if you try to create the 6th, the tooling would report you that the 6th app could not be configured. !cannot-create-6th-app.png! It unfortunately does not tell you that there is a limit of 5 applications. We should tell the user that he can only create 5 applications. -- 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, 11 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-10236) Creating a 2nd jenkins application fails

by Andre Dietisheim (Created) (JIRA)

Creating a 2nd jenkins application fails ---------------------------------------- Key: JBIDE-10236 URL: https://issues.jboss.org/browse/JBIDE-10236 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- 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, 11 months

5
5
0 / 0

[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] 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] 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-10063) Forge creates invalid web.xml

by Burr Sutter (Created) (JIRA)

Forge creates invalid web.xml ----------------------------- Key: JBIDE-10063 URL: https://issues.jboss.org/browse/JBIDE-10063 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Environment: Tools 3.3.M4 Reporter: Burr Sutter Forge console (plug-in) - new-project --named forgeProject2 --topLevelPackage com.burrsutter.forgeProject2 - scaffold setup creates a web.xml with the following errors (according to Eclipse) - error: Attribute location references to /404.jsp that does not exist in web content - error: Attribute location references to /500.jsp that does not exist in web content -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8700) Add Configure>Detect Project Configuration menu to runtime plugin

by Snjezana Peco (JIRA)

Add Configure>Detect Project Configuration menu to runtime plugin ----------------------------------------------------------------- Key: JBIDE-8700 URL: https://issues.jboss.org/browse/JBIDE-8700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 The action would detect different project configurations. For the first time, it would detect CDI based on the existence of cdi-api in the project's classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-10177) web.xml validator should be aware of JSF mappings

by Alexey Kazakov (Created) (JIRA)

web.xml validator should be aware of JSF mappings ------------------------------------------------- Key: JBIDE-10177 URL: https://issues.jboss.org/browse/JBIDE-10177 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M4 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 1. Create JSF2 KickStart project. 2. Create 404.xhtml page in WebContent folder 3. Add the following code to the end of web.xml file: {code} <error-page> <error-code>404</error-code> <location>/404.jsf</location> </error-page> {code} There should not be any error/warning markers on /404.jsf. This location should be mapped to the 404.xhtml file. But right now I get: "error: Attribute location references to /404.jsp that does not exist in web content" error message. -- 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

10
14
0 / 0

[JBoss JIRA] (JBIDE-9998) Make new Forge Runtime Layout Work with JBT

by Koen Aers (Created) (JIRA)

Make new Forge Runtime Layout Work with JBT ------------------------------------------- Key: JBIDE-9998 URL: https://issues.jboss.org/browse/JBIDE-9998 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.M4 Forge Runtime changed module layout yesterday, resulting in the current Forge Runtime SNAPSHOT builds not working with the tools. -- 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
5
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 November 2011