October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12562) org.sourceforge.pmd.eclipse has invalid OSGi MANIFEST.MF

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-12562: ------------------------------------ Summary: org.sourceforge.pmd.eclipse has invalid OSGi MANIFEST.MF Key: JBIDE-12562 URL: https://issues.jboss.org/browse/JBIDE-12562 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.0.0.Alpha1 Environment: JBT 4.0.0.Alfa1 Reporter: Jiri Peterka Assignee: Nick Boldt Fix For: 4.0.0.Alpha2 org.sourceforge.pmd.eclipse is not valid OSGI bundle and cannot be loaded as target runtime in eclipse It contains only: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 10.0-b19 (Sun Microsystems Inc.) -- 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, 5 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-12633) Support for JAX-RS Application subclassing with configuration in web.xml

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12633: ------------------------------------- Summary: Support for JAX-RS Application subclassing with configuration in web.xml Key: JBIDE-12633 URL: https://issues.jboss.org/browse/JBIDE-12633 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 4.0.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Alpha2 As described in https://docs.jboss.org/author/display/AS7/JAX-RS+Reference+Guide, the plugin should support the following use case: {quote} Subclassing javax.ws.rs.core.Application and using web.xml If you do not wish to use @ApplicationPath but still need to subclass Application you can set up the JAX-RS mapping in web.xml: {quote} {code} public class MyApplication extends Application { } {code} {code} <servlet-mapping> <servlet-name>com.acme.MyApplication</servlet-name> <url-pattern>/hello/*</url-pattern> </servlet-mapping> {code} -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] (JBDS-2290) Add m2e-apt 1.0.1 to JBDS 6.0.0.Alpha2

by Fred Bricon (JIRA)

Fred Bricon created JBDS-2290: --------------------------------- Summary: Add m2e-apt 1.0.1 to JBDS 6.0.0.Alpha2 Key: JBDS-2290 URL: https://issues.jboss.org/browse/JBDS-2290 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 6.0.0.Alpha2 Reporter: Fred Bricon Fix For: 6.0.0.Alpha2 I thought m2e-apt 1.0.1 was added to the JBDS installer, as requested in JBIDE-12649 but 1.0.0 is still shipped with current JBDS 6.0.0.Alpha2. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12720) delete ancient drools and guvnor docs from JBT SVN repo; place README pointing at updated docs

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12720: ---------------------------------- Summary: delete ancient drools and guvnor docs from JBT SVN repo; place README pointing at updated docs Key: JBIDE-12720 URL: https://issues.jboss.org/browse/JBIDE-12720 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 4.0.0.Alpha2 Reporter: Nick Boldt Assignee: Kris Verlaenen I asked of [~KrisVerlaenen] and [~ge0ffrey]: {quote} Do you still need the drools/guvnor doc in JBoss Tools' SVN repo? Or have you migrated that to github? Code's here: https://svn.jboss.org/repos/jbosstools/trunk/drools/docs/ Also in our git-svn mirror here: https://github.com/jbosstools/jbosstools-svn-mirror/tree/trunk/drools/docs Looks like it hasn't changed in 10 months. We'd like to delete it from trunk (but leave it in older branches) as part of our cleanup / git migration. Do you need it? Can you migrate it out ASAP? {quote} And [~ge0ffrey] replied: {quote} This is the first time I hear about that svn repository. No objections of me to delete that. <irrelavant>We do still need our old drools svn repository (as it's the best place to get 4.x releases code from etc), but that's a different svn repo.</irrelavant> Kris, can it be deleted? --- If we want them as a separate docs, they should be under https://github.com/droolsjbpm/droolsjbpm-tools/ as a module droolsjbpm-tools-docs similar to https://github.com/droolsjbpm/guvnor/ with the module guvnor-docs But IIRC, I believe the introduction docs and/or expert docs already describe the eclipse tooling. http://www.jboss.org/drools/documentation {quote} -- 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, 5 months

1
6
0 / 0

[JBoss JIRA] (JBIDE-12761) Target-platfom should contain depdencies in the "minimal compatible" version

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12761: -------------------------------------- Summary: Target-platfom should contain depdencies in the "minimal compatible" version Key: JBIDE-12761 URL: https://issues.jboss.org/browse/JBIDE-12761 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: target-platform Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 4.0.0.Beta1 Currently, TP contains the latest version of all dependencies. However, JBT can run on lower versions of Eclipse. It happens that developer introduce a depdendency on a very recent version when it's not necessary because they rely on our target-platform. Instead, TP should contain the minimal versions of all dependencies that are compatible with JBoss Tools. Then developers can rely on very old version, and when necessary, request usage of new one and break dependencies. Installation tests are already there to verify installation on latest versions of Eclipse. -- 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, 5 months

3
22
0 / 0

[JBoss JIRA] (JBIDE-11404) Get basic "mvn clean install" to work with everything developers want

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11404: -------------------------------------- Summary: Get basic "mvn clean install" to work with everything developers want Key: JBIDE-11404 URL: https://issues.jboss.org/browse/JBIDE-11404 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 3.3.0.Beta3 We should set up the default profiles so that developers can use simply "mvn clean install" to build their project. That will require to see what they usually want to build, and to change default profiles to match their usual needs. -- 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, 5 months

5
33
0 / 0

[JBoss JIRA] (JBIDE-12847) VPE throws StackOverflowError and visual part is blank

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-12847: ------------------------------------- Summary: VPE throws StackOverflowError and visual part is blank Key: JBIDE-12847 URL: https://issues.jboss.org/browse/JBIDE-12847 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Yahor Radtsevich Assignee: Denis Golovin Fix For: 3.3.2, 4.0.0.Beta1 Attachments: screenshot.png # Create new RichFaces project from JBoss Central View # Open richfaces-webapp/src/main/webapp/WEB-INF/templates/mobile.xhtml in VPE *Result:* VPE is blank: !screenshot.png|thumbnail! {code} java.lang.StackOverflowError at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466) at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694) at java.util.regex.Pattern$Branch.match(Pattern.java:4502) {code} -- 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, 5 months

1
1
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

13 years, 5 months

5
29
0 / 0

[JBoss JIRA] (JBIDE-12803) Publishing to ... OpenShift Server - after project rename

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12803: ----------------------------------- Summary: Publishing to ... OpenShift Server - after project rename Key: JBIDE-12803 URL: https://issues.jboss.org/browse/JBIDE-12803 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Burr Sutter Assignee: Andre Dietisheim Attachments: 2012-10-04_1859.png Using JBDS, I used Refactor - Rename Maven Artifact and Refactor - Rename to change my project name - this project had previusly been deployed to Openshift and now the Full Publish fails. The workaround is to double-click on the Openshift server adapter (Servers Tab) and reset which project it is tied to. -- 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, 5 months

3
5
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, 5 months

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