June 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8803) the build system need a jre5 installed

by Feng Qian (JIRA)

the build system need a jre5 installed -------------------------------------- Key: JBIDE-8803 URL: https://issues.jboss.org/browse/JBIDE-8803 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Reporter: Feng Qian Assignee: Nick Boldt Fix For: 3.2.1.M1 https://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_stable_branch.tests... There are three ws junit tests failed. Because in hudson system, no jre5 location. the error is: The JRE5 location is not right I had remebered, some time ago, in 3.2-trunk codes, https://issues.jboss.org/browse/JBIDE-6581 we need a system property for jre5, I will use the codes to get it's location: System.getProperty("jbosstools.test.jre.5", ""); I think for the 3.2 branch, we don't set the jre5 for the build, right? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-4727) Support distribution defining "New Project" dependencies

by Pete Muir (JIRA)

Support distribution defining "New Project" dependencies -------------------------------------------------------- Key: JBIDE-4727 URL: https://jira.jboss.org/jira/browse/JBIDE-4727 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Pete Muir Summary: Move the responsibility for defining a "New Seam Project"'s dependencies (libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to define the dependencies. Use Maven POM profiles to support different use cases for Seam projects. Reason: Currently JBoss Tools defines the project dependencies which causes issues very time Seam changes either the dependency set of a new seam project, or the layout of libraries in the distribution. Use Maven 2 POM format as it is already a well defined and understood model. Use of Maven POM profiles can further increase the flexibility and support various use cases for Seam (for example, Seam with jBPM or Seam with ICEFaces). Details: JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml, ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite modules of an EAR project. The standard Maven scopes are used: compile to indicate compile/runtime dependencies of the project, test to indicate extra dependencies required in the test project. Maven profiles are used to define additional dependency sets for new seam projects, allowing the user to optionally add extra dependencies to his project. To make this extensible, and not require JBossTools to use a well-known list of profile ids, an xml namespace will be used to add additional metadata to the profile. This allows JBossTools to identify the possible profiles: <profile> <id>drools5</id> <jbt:profile> <jbt:description>Drools 5 support (Tech Preview)</jbt:description> </jbt:profile>  </profile> <profile> <id>ICEFaces</id> <jbt:profile> <jbt:description>ICEFaces</jbt:description> </jbt:profile>  </profile> JBossTools can recognize the jbt:profile element, and use the jbt:description element to as a descriptive element to present to the user: [x] ICEFaces [x] Drools 5 support (Tech Preview) displayed in the New Seam Project Wizard. We should allow for additional information to be placed in the POM and in the future beyond dependency information. For example, additional configuration files to include in the generated project, however this is not a critical feature. We should also consider allowing JBoss Tools to retrieve the POMs from a Maven repository. This would require a user to simply specify the version of Seam they require, and have JBoss Tools download the seam-gen artifact containing all templates and resources. -- 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

11 years, 7 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9181) JSP tags shows as unknown tags in VPE

by Maxim Areshkau (JIRA)

JSP tags shows as unknown tags in VPE ------------------------------------- Key: JBIDE-9181 URL: https://issues.jboss.org/browse/JBIDE-9181 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Maxim Areshkau Assignee: Yahor Radtsevich Priority: Critical all jsp tags shows as unknow tags in VPE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

7
26
0 / 0

[JBoss JIRA] Created: (JBIDE-8924) Code completion for EL functions doesn't work for complex ELs.

by Alexey Kazakov (JIRA)

Code completion for EL functions doesn't work for complex ELs. -------------------------------------------------------------- Key: JBIDE-8924 URL: https://issues.jboss.org/browse/JBIDE-8924 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.3.0.M2 Attachments: bug.png 1. Create Seam web project. 2. Open login.xhtml 3. Add #{rich:findComponent().|} + Ctrl+Space -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

5
17
0 / 0

[JBoss JIRA] Created: (JBIDE-8970) Maven Library Provider and basic ui for "Create New (xyz-faceted) Project"

by Max Rydahl Andersen (JIRA)

Maven Library Provider and basic ui for "Create New (xyz-faceted) Project" --------------------------------------------------------------------------- Key: JBIDE-8970 URL: https://issues.jboss.org/browse/JBIDE-8970 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 3.3.0.M3 We already have some basic code for Maven library providers that sets up dependencies in pom.xml based on facet id's on project creation. Look into what is missing and see what we can do and what m2e might need to have improvements for. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8573) Code completion for all the available validator IDs for <s:validateForm validatorId="|" />

by Alexey Kazakov (JIRA)

Code completion for all the available validator IDs for <s:validateForm validatorId="|" /> ------------------------------------------------------------------------------------------ Key: JBIDE-8573 URL: https://issues.jboss.org/browse/JBIDE-8573 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x See http://docs.jboss.org/seam/3/faces/latest/reference/en-US/html/components... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8574) OpenOn for corresponding validator for <s:validateForm validatorId="validatorID" />

by Alexey Kazakov (JIRA)

OpenOn for corresponding validator for <s:validateForm validatorId="validatorID" /> ----------------------------------------------------------------------------------- Key: JBIDE-8574 URL: https://issues.jboss.org/browse/JBIDE-8574 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x For example Ctrl+Click on locationValidator within <s:validateForm validatorId="locationValidator" /> should open: @FacesValidator("locationValidator") public class LocationValidator implements Validator {...} See http://docs.jboss.org/seam/3/faces/latest/reference/en-US/html/components... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
10
0 / 0

[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

11 years, 7 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

11 years, 7 months

6
19
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

11 years, 7 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2011