September 2012 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1659) If set as default, java 1.5 is used even if 1.6 is chosen during installation

by Martin Malina (JIRA)

If set as default, java 1.5 is used even if 1.6 is chosen during installation ----------------------------------------------------------------------------- Key: JBDS-1659 URL: https://issues.jboss.org/browse/JBDS-1659 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 4.1.0.M1 Environment: jbdevstudio-product-macosx-cocoa-x86_64-4.1.0.v201105091943R-H400-M1.jar Mac OS X 10.5 Leopard Reporter: Martin Malina If java 1.5 is set as default in the Java Preferences utility and you select java 1.6 during JBDS installation, it is still started with 1.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

5
29
0 / 0

[JBoss JIRA] Created: (JBIDE-8993) Unable to run DroolTest.java because of missing org.eclipse.jdt.core*.jar in project classpath

by Vlado Pakan (JIRA)

Unable to run DroolTest.java because of missing org.eclipse.jdt.core*.jar in project classpath ---------------------------------------------------------------------------------------------- Key: JBIDE-8993 URL: https://issues.jboss.org/browse/JBIDE-8993 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M1 Environment: Linux 32bit, Sun JDK 1.6_25, jbosstools-3.3.0.M1a.aggregate-Update-2011-05-11_15-56-28-H2359 Reporter: Vlado Pakan Priority: Critical Fix For: 3.3.0.M1 When creating new Drools Runtime from Drools plugin bundled to JBT org.eclipse.jdt.core*.jar file is not included in this runtime and therefore when running DroolTest.java this error is displayed in console: org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.rule.builder.dialect.java.JavaDialectConfiguration' at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:277) at org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:262) at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:175) at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:153) at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:218) at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:146) at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilder(KnowledgeBuilderFactoryServiceImpl.java:34) at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilder(KnowledgeBuilderFactory.java:46) at com.sample.DroolsTest.readKnowledgeBase(DroolsTest.java:39) at com.sample.DroolsTest.main(DroolsTest.java:23) Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:93) at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:54) at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:273) ... 9 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

6
19
0 / 0

[JBoss JIRA] (JBDS-2295) provide job to test automated installation of JBDS "BYOE" into Eclipse 4.2.0, 4.2.1, Juno JEE bundle, Juno JEE bundle SR1, etc.

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2295: -------------------------------- Summary: provide job to test automated installation of JBDS "BYOE" into Eclipse 4.2.0, 4.2.1, Juno JEE bundle, Juno JEE bundle SR1, etc. Key: JBDS-2295 URL: https://issues.jboss.org/browse/JBDS-2295 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: installer, P2 Enabled Product Affects Versions: 6.0.0.Alpha2 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 6.0.0.Beta1 Similar to this job [1], we should be testing this installation path so that we know it works on Eclipse Platform Binary 4.2.0, 4.2.1, 4.2.2 (when available in Feb 2013) as well as Eclipse Juno R, SR1, SR2 (also Feb 2013). [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4791) Properties list in Properties view disappears when the user clicks a tab in CSS Properties view

by Olga Chukhutsina (JIRA)

Properties list in Properties view disappears when the user clicks a tab in CSS Properties view ----------------------------------------------------------------------------------------------- Key: JBIDE-4791 URL: https://jira.jboss.org/jira/browse/JBIDE-4791 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M3 Environment: Ubuntu 8.10, JBossTools revision 17062 Reporter: Olga Chukhutsina Assignee: Sergey Dzmitrovich Properties list disappears from Properties view when the user clicks tabs in CSS Properties view. Steps: Choose some selector in CSS file>Text/Font tab is opened in CSS Properties view by default and the properties list in Properties view is displayed>choose another tab in CSS Properties view(e.g Background )>now properties list in Properties view is not shown any more -- 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

13 years, 4 months

5
8
0 / 0

[JBoss JIRA] (JBDS-2336) JBDS Mylyn plugin inconsistency - RH bugzilla allows user to change profile, JBoss JIRA does not

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2336: ---------------------------------- Summary: JBDS Mylyn plugin inconsistency - RH bugzilla allows user to change profile, JBoss JIRA does not Key: JBDS-2336 URL: https://issues.jboss.org/browse/JBDS-2336 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification Affects Versions: 6.0.0.Alpha2 Environment: Version: 6.0.0.Alpha2 Build id: Alpha2-v20120924-2110-B28 Build date: 20120924-2110 Reporter: Len DiMaggio Priority: Minor Fix For: 6.0.0.Beta1 See attached screenshots. -- 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

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10777) Use Sonar for QA

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-10777: -------------------------------------- Summary: Use Sonar for QA Key: JBIDE-10777 URL: https://issues.jboss.org/browse/JBIDE-10777 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.1.2 Environment: any Reporter: Mickael Istria Priority: Minor Sonar provides a very powerful tool to get report about tests, code coverage, and static analysis in a project (errors, duplications...). It is easy to use, there is a nice integration with Maven and Hudson/Jenkins. It provides reporting tools for everything existing in the Java world, and more. Adding Sonar to Hudson really helps to make code better. http://www.sonarsource.org/ -- 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, 4 months

5
10
0 / 0

[JBoss JIRA] (JBIDE-10767) Renaming java element does not force to re-validate related resources

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10767: -------------------------------------- Summary: Renaming java element does not force to re-validate related resources Key: JBIDE-10767 URL: https://issues.jboss.org/browse/JBIDE-10767 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core, jsp/jsf/xml source editing Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 1. Create an EAR Seam 2 project 2. Open home.xhtml 3. Add #{authenticator.authenticate()} 4. Save the file 5. Open Authenticator.java 6. Rename Authenticator.authenticate() to authenticateNew() using refactoring. 7. #{authenticator.authenticate()} is refactored to #{authenticator.authenticateNew()}. That's good. But there is a marker now: "authenticate" is not recognized. This is not correct since this EL was updated to #{authenticator.authenticateNew()}. -- 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, 4 months

2
8
0 / 0

[JBoss JIRA] (JBIDE-10703) Follow common pattern in bundle activator classes

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-10703: --------------------------------------------- Summary: Follow common pattern in bundle activator classes Key: JBIDE-10703 URL: https://issues.jboss.org/browse/JBIDE-10703 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 1. Static instance of plugin implementation should be assigned in constructor, not in start() method. 2. Static instance of plugin implementation should not be set to null in method stop() as it may cause logging NullPointerException at Eclipse shutdown (we already had such issues, mostly reproduced in automatic tests). 3. Extend BaseUIPlugin in plugins that depend on common module. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11424) ConcurrentModificationException in Error Log after creating JSF2 Kickstart Project

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11424: ------------------------------------ Summary: ConcurrentModificationException in Error Log after creating JSF2 Kickstart Project Key: JBIDE-11424 URL: https://issues.jboss.org/browse/JBIDE-11424 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.Beta2 Environment: JBDS5Beta2 #115, L64 Reporter: Jiri Peterka Assignee: Alexey Kazakov Fix For: 3.3.0.Beta3 java.util.ConcurrentModificationException at java.util.Hashtable$Enumerator.next(Hashtable.java:1031) at org.eclipse.wst.html.core.internal.modelquery.CMNamedNodeMapForBuddySystem.makeBuddySystem(CMNamedNodeMapForBuddySystem.java:100) at org.eclipse.wst.html.core.internal.modelquery.CMDocumentForBuddySystem$Elements.<init>(CMDocumentForBuddySystem.java:36) at org.eclipse.wst.html.core.internal.modelquery.CMDocumentForBuddySystem.getElements(CMDocumentForBuddySystem.java:90) at org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.SimpleAssociationProvider.getCMElementDeclaration(SimpleAssociationProvider.java:45) at org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.ModelQueryImpl.getCMElementDeclaration(ModelQueryImpl.java:116) at org.eclipse.wst.html.core.internal.modelquery.HTMLModelQueryImpl.getCMElementDeclaration(HTMLModelQueryImpl.java:152) at org.eclipse.wst.xml.core.internal.document.ElementImpl.getDeclaration(ElementImpl.java:369) at org.eclipse.wst.xml.core.internal.document.CMNodeUtil.getElementDeclaration(CMNodeUtil.java:40) at org.eclipse.wst.html.core.internal.document.HTMLModelParserAdapter.canContain(HTMLModelParserAdapter.java:86) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertNode(XMLModelParser.java:1327) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStartTag(XMLModelParser.java:1402) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStartTag(XMLModelParser.java:1499) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.insertStructuredDocumentRegion(XMLModelParser.java:1510) at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2354) at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.internalSetNewDocument(DOMModelImpl.java:661) at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.setStructuredDocument(DOMModelImpl.java:936) at org.eclipse.wst.sse.core.internal.model.AbstractModelLoader.createModel(AbstractModelLoader.java:127) at org.eclipse.wst.sse.core.internal.FileBufferModelManager.getModel(FileBufferModelManager.java:725) at org.eclipse.wst.sse.core.internal.FileBufferModelManager.getModel(FileBufferModelManager.java:685) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._doCommonGetModel(ModelManagerImpl.java:544) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._commonGetModel(ModelManagerImpl.java:508) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._commonGetModel(ModelManagerImpl.java:481) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getModelForRead(ModelManagerImpl.java:1419) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:379) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:222) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:211) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:200) at org.jboss.tools.jsf.web.validation.composite.CompositeComponentValidator.validateResource(CompositeComponentValidator.java:188) at org.jboss.tools.jsf.web.validation.composite.CompositeComponentValidator.validateAll(CompositeComponentValidator.java:167) at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:132) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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, 4 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12335) Seam config validation errors not found

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12335: ----------------------------------------- Summary: Seam config validation errors not found Key: JBIDE-12335 URL: https://issues.jboss.org/browse/JBIDE-12335 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.4.0.M1 Reporter: Jaroslav Jankovič Assignee: Alexey Kazakov Fix For: 3.4.0.M1 Seam config validation errors are not found when importing the project. Cleaning the build doesn't help either. -- 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, 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 September 2012