December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7011) Mavenized Seam Web project can't be created using m2eclipse 0.11

by Snjezana Peco (JIRA)

Mavenized Seam Web project can't be created using m2eclipse 0.11 ---------------------------------------------------------------- Key: JBIDE-7011 URL: https://jira.jboss.org/browse/JBIDE-7011 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.M1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.2.0.Beta The m2eclipse Java configurator ignores compiler setting in a parent project and uses the default setting (1.4) which causes an error when creating a Java facet >= 5.0/1.5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-1343) ModeShape plugin needs to have its modeshape client jar replaced with the SOA-P ER3 build

by Dan Florian (JIRA)

ModeShape plugin needs to have its modeshape client jar replaced with the SOA-P ER3 build ----------------------------------------------------------------------------------------- Key: JBDS-1343 URL: https://jira.jboss.org/browse/JBDS-1343 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Modeshape Reporter: Dan Florian Assignee: Dan Florian Priority: Blocker Fix For: 4.0.0.Beta1 The current ModeShape rest client jar is out-of-date. It needs to be replaced by the modeshape-client.jar being built from SOA-P. Note, the rest client jar is being replace by a different client jar that contains both the rest client and jdbc client interfaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6984) Upgrade ModeShape Plugin To Use The Latest ModeShape JDBC Jar (Currently 2.2)

by Dan Florian (JIRA)

Upgrade ModeShape Plugin To Use The Latest ModeShape JDBC Jar (Currently 2.2) ----------------------------------------------------------------------------- Key: JBIDE-6984 URL: https://jira.jboss.org/browse/JBIDE-6984 Project: Tools (JBoss Tools) Issue Type: Task Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Dan Florian Fix For: 3.2.0.Beta The ModeShape JBT plugin is currently using a manually built ModeShape project REST client jar with dependencies based on a ModeShape 2.1 snapshot release. A ModeShape JDBC jar is being built automatically by ModeShape and contains all the dependencies that the ModeShape JBT plugin needs except net.jcip.annotations. Also the ModeShape JDBC jar is significantly smaller in size. The net.jcip.annotations library is also being used by Teiid Designer so that library needs to be available from a common location within JBT and another ticket will be written to address that. Having the ModeShape JBT plugin use the JDBC jar may also benefit Teiid Designer as users of Designer may want to also use the ModeShape JDBC driver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7778) JBoss Tools update site aggregator fails to resolve Eclipse platform dependency

by Nick Boldt (JIRA)

JBoss Tools update site aggregator fails to resolve Eclipse platform dependency ------------------------------------------------------------------------------- Key: JBIDE-7778 URL: https://jira.jboss.org/browse/JBIDE-7778 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.2.0.Beta2 Reporter: Nick Boldt Assignee: Max Andersen Latest target platform repo contains: sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources.source_3.6.0.R36x_v20100825-0600.jar sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources.source_3.6.0.R36x_v20100928-0457.jar sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources.source_3.6.1.R36x_v20101007-1215.jar sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources.win32.x86_3.5.100.v20100505-1345.jar sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100825-0600.jar sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources_3.6.0.R36x_v20100928-0457.jar sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/updates/target-platform/latest/plugins/org.eclipse.core.resources_3.6.1.R36x_v20101007-1215.jar Yet something is requiring this version: [ERROR] Internal error: java.lang.RuntimeException: Could not download artifacts from any repository [ERROR] osgi.bundle,org.eclipse.core.resources,3.6.0.v20100526-0737 This was not a requirement before Build #21 (Nov 26, 2010 10:19:17 PM): http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/devstu... But has been failing since then. Need to track down which plugin(s) and/or feature(s) depend on this specific version of the plugin, and fix that manifest so it can use [3.6.0,3.7.0) instead. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7116) BPEL Editor not seeing message structure when imported into WSDL

by Jeff DeLong (JIRA)

BPEL Editor not seeing message structure when imported into WSDL ---------------------------------------------------------------- Key: JBIDE-7116 URL: https://jira.jboss.org/browse/JBIDE-7116 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Environment: JBTools3.2Beta1 Eclipse 3.6 on Mac Reporter: Jeff DeLong I have a WSDL generated from Savara. It looks like this: <wsdl:definitions name="PolicyQuoteProcessService" targetNamespace="http://www.pi4soa.org/PolicyQuote" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://www.pi4soa.org/PolicyQuote" xmlns:pcs="http://www.example.org/policyQuoteCalculationService" xmlns:pol="http://www.example.org/policyQuote" xmlns:pes="http://www.example.org/policyQuoteEntityService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cred="http://creditagency.com/creditCheck" xmlns:pps="http://www.example.org/policyQuoteProcessService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:dmv="http://dmv.com/drivingRecord"> <types xmlns="http://schemas.xmlsoap.org/wsdl/"> <schema xmlns="http://www.w3.org/2001/XMLSchema"> <import namespace="http://www.example.org/policyQuote" schemaLocation="../schema/policyQuote.xsd"/> <import namespace="http://creditagency.com/creditCheck" schemaLocation="../schema/creditCheck.xsd"/> <import namespace="http://dmv.com/drivingRecord" schemaLocation="../schema/drivingRecord.xsd"/> </schema> </types> <wsdl:message name="receivePolicyQuoteRequest"> <wsdl:part name="content" element="pol:policyQuote"> </wsdl:part> </wsdl:message> ... Where policyQuote schema is imported. When I create a Variable in the BPEL Editor, it does not see the structure of the message. This is a big problem, since with out the message details it is impossible to do Assign / Copy. I will attach the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-7767) tests broken in 7.1 branch

by Nick Boldt (JIRA)

tests broken in 7.1 branch -------------------------- Key: JBIDE-7767 URL: https://jira.jboss.org/browse/JBIDE-7767 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.Beta2 Reporter: Nick Boldt Assignee: Barry LaFond [ERROR] The project org.jboss.tools:tests.all:0.0.1-SNAPSHOT (/mnt/hudson_workspace/workspace/jbosstools-teiid-designer-7.1_stable_branch/sources/tests/pom.xml) has 2 errors [ERROR] 'modules.module[5]' specifies duplicate child module org.teiid.designer.core.test @ line 20, column 11 [ERROR] 'modules.module[29]' specifies duplicate child module org.teiid.designer.vdb.test @ line 44, column 11 http://hudson.qa.jboss.com/hudson/job/jbosstools-teiid-designer-7.1_stabl... Not sure what's amiss here, but have a look at the poms mentioned above and see what's causing the duplicate. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6398) SeamValidatorsAllTests fail intermittently on slaves soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64 for both JBT & JBDS builds

by Nick Boldt (JIRA)

SeamValidatorsAllTests fail intermittently on slaves soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64 for both JBT & JBDS builds -------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6398 URL: https://jira.jboss.org/browse/JBIDE-6398 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.1.1 Reporter: Nick Boldt Not sure why these tests appear here: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... (vmg20-rhel5-x86) Then disappear (failed? disabled? missing?) for all builds since. And, similarly: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (vmg20-rhel5-x86) But once again disappear (failed? disabled? missing?) for these builds: #109, 110, 111 (soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64) I wonder if the problem is one of configuration of the slaves (bad config? low ram? low disk?) or that the tests are too greedy/misconfigured? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6944) Related preferences pages are not populated with imported runtimes.

by Vlado Pakan (JIRA)

Related preferences pages are not populated with imported runtimes. ------------------------------------------------------------------- Key: JBIDE-6944 URL: https://jira.jboss.org/browse/JBIDE-6944 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration, JBossAS Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.v201008261621R-H420-M2 Reporter: Vlado Pakan When importing runtimes as described in related jira https://jira.jboss.org/browse/JBIDE-6119. Imported runtimes preference pages are not populated with imported runtimes i. e. when user clicks on the WTP Runtime link and WTP Runtimes were imported there are no imported WTP runtimes displayed in table on WTP Runtime preference page. After preferences dialog is reopened all imported runtimes are correctly displayed on their related Proprties pages -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7318) NullPointerException occurreswhile running JUnit test org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist

by Victor Rubezhny (JIRA)

NullPointerException occurreswhile running JUnit test org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7318 URL: https://jira.jboss.org/browse/JBIDE-7318 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Beta1 Reporter: Victor Rubezhny Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 !ENTRY org.eclipse.wst.sse.ui 2 0 2010-10-12 17:58:46.336 !MESSAGE The ''org.jboss.tools.jst.jsp.proposalComputer.xhtmlEL'' proposal computer from the ''org.jboss.tools.jst.jsp'' plug-in did not complete normally. The extension has thrown a runtime exception. !STACK 0 java.lang.NullPointerException at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.getProposals(AbstractELCompletionEngine.java:106) at org.jboss.tools.jst.web.kb.PageProcessor.getProposals(PageProcessor.java:164) at org.jboss.tools.jst.web.kb.PageProcessor.getProposals(PageProcessor.java:61) at org.jboss.tools.jst.jsp.contentassist.computers.XmlELCompletionProposalComputer.addELPredicateProposals(XmlELCompletionProposalComputer.java:357) at org.jboss.tools.jst.jsp.contentassist.computers.XmlELCompletionProposalComputer.addAttributeValueProposals(XmlELCompletionProposalComputer.java:143) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeAttributeValueProposals(AbstractXMLCompletionProposalComputer.java:594) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:399) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:169) at org.jboss.tools.jst.jsp.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:81) at org.jboss.tools.jst.jsp.contentassist.computers.FaceletsELCompletionProposalComputer.computeCompletionProposals(FaceletsELCompletionProposalComputer.java:85) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:294) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:455) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:252) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:126) at org.jboss.tools.jst.jsp.test.TestUtil.collectProposals(TestUtil.java:133) at org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist(SeamELContentAssistTestCase.java:574) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4496) Seam builder somtimes creates components without any declarations at all.

by Alexey Kazakov (JIRA)

Seam builder somtimes creates components without any declarations at all. ------------------------------------------------------------------------- Key: JBIDE-4496 URL: https://jira.jboss.org/jira/browse/JBIDE-4496 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.M4 Sometimes our tests fails because seam model is not correct. For example we have: @Name("comp1") public class Comp1 {...} Seam builder creates "comp1" component but getJavaDeclaration() return null even if the project is correct and all nedded libs are in classpath. It's hard to reproduce this issue. We need to investigate it and found the resoun of this bug. Looks like thread racing is responsible for that. -- 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

15 years, 4 months

3
8
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 December 2010