April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13061) Freemarker ui tests are failing on JDK 1.7

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13061: ------------------------------------ Summary: Freemarker ui tests are failing on JDK 1.7 Key: JBIDE-13061 URL: https://issues.jboss.org/browse/JBIDE-13061 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 4.0.0.Beta2 Reporter: Jiri Peterka Assignee: Jiri Peterka Fix For: 4.0.0.Beta2 There is a profile wrongly set AWT toolkit in https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... -- 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

1 week, 1 day

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6878) Seam does not work with JSF 2.0 faces-config.xml

by Alexey Kazakov (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBIDE-6878 URL: https://jira.jboss.org/browse/JBIDE-6878 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x This is an issue of Seam runtime. See https://jira.jboss.org/browse/JBSEAM-4637 But let's have a duplicate it in JBT JIRA to track JBSEAM-4637 -- 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

3 weeks, 6 days

3
5
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {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

1 month, 3 weeks

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Jim Tyrrell (JIRA)

Console not showing up when staritng a EAP/SOA-P Instance --------------------------------------------------------- Key: JBDS-983 URL: https://jira.jboss.org/jira/browse/JBDS-983 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.M4 Reporter: Jim Tyrrell For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- 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

3 months, 1 week

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- 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 months, 1 week

3
7
0 / 0

[JBoss JIRA] (JBIDE-17220) Sometimes 'Experimental Features' of JBoss Tools gets visible in Preferences

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17220?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-17220: ------------------------------------- Assignee: Denis Golovin > Sometimes 'Experimental Features' of JBoss Tools gets visible in Preferences > ---------------------------------------------------------------------------- > > Key: JBIDE-17220 > URL: https://issues.jboss.org/browse/JBIDE-17220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Beta2 > > > Sometimes after partial installation of JBoss Tools some experimental features gets visible in: > * Preferences > * Properties > It happens because common/jst/jsf bundles installed as direct dependencies without common.model.ui.capabilities bundle which hides them in eclipse UI. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17220) Sometimes 'Experimental Features' of JBoss Tools gets visible in Preferences

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17220?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17220: ---------------------------------- Fix Version/s: 4.2.0.Beta2 > Sometimes 'Experimental Features' of JBoss Tools gets visible in Preferences > ---------------------------------------------------------------------------- > > Key: JBIDE-17220 > URL: https://issues.jboss.org/browse/JBIDE-17220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Beta2 > > > Sometimes after partial installation of JBoss Tools some experimental features gets visible in: > * Preferences > * Properties > It happens because common/jst/jsf bundles installed as direct dependencies without common.model.ui.capabilities bundle which hides them in eclipse UI. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17220) Sometimes 'Experimental Features' of JBoss Tools gets visible in Preferences

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-17220: ------------------------------------- Summary: Sometimes 'Experimental Features' of JBoss Tools gets visible in Preferences Key: JBIDE-17220 URL: https://issues.jboss.org/browse/JBIDE-17220 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Reporter: Denis Golovin Sometimes after partial installation of JBoss Tools some experimental features gets visible in: * Preferences * Properties It happens because common/jst/jsf bundles installed as direct dependencies without common.model.ui.capabilities bundle which hides them in eclipse UI. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17207) Run tests on all major OS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17207: ---------------------------------------- {quote}have you come across any specific issues when using different platforms in Boston Jenkins?{quote} I don't know what the Boston Jenkins is ;) > Run tests on all major OS > ------------------------- > > Key: JBIDE-17207 > URL: https://issues.jboss.org/browse/JBIDE-17207 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Alexey Kazakov > Fix For: 4.2.0.Beta2, 4.2.0.CR1 > > > Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac. > For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200. > We don't have to run them every day. Maybe once a week or month? > cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria] -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17218) [compilation]fix openshift build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17218?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17218. --------------------------------- verified on master. closing. > [compilation]fix openshift build > -------------------------------- > > Key: JBIDE-17218 > URL: https://issues.jboss.org/browse/JBIDE-17218 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, server > Affects Versions: 4.2.0.Beta1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.Beta2 > > > openshif build is broken right now > {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure: > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[53] > [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyButtonCommand; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyButtonCommand cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[54] > [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyComboCommand; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyComboCommand cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[55] > [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyCommand; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyCommand cannot be resolved > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[221] > [ERROR] browseDestButton.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, null, 0, 100, 0)); > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[223] > [ERROR] deployFolderText.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, 0, 0, browseDestButton, -5)); > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[240] > [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute( > [ERROR] ^^^^^^^ > [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetProjectCommand) > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[247] > [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetOverrideCommand(server)); > [ERROR] ^^^^^^^ > [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetOverrideCommand) > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[254] > [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetRemoteCommand(server)); > [ERROR] ^^^^^^^ > [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetRemoteCommand) > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[260] > [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetDeployFolderCommand(server)); > [ERROR] ^^^^^^^ > [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetDeployFolderCommand) > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[303] > [ERROR] public class SetRemoteCommand extends ServerWorkingCopyPropertyCommand { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] ServerWorkingCopyPropertyCommand cannot be resolved to a type > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[311] > [ERROR] public class SetProjectCommand extends ServerWorkingCopyPropertyComboCommand { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] ServerWorkingCopyPropertyComboCommand cannot be resolved to a type > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[318] > [ERROR] protected void postOp(int type) { > [ERROR] ^^^^^^^^^^^^^^^^ > [ERROR] The method postOp(int) of type OpenShiftServerEditorSection.SetProjectCommand must override or implement a supertype method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[323] > [ERROR] public class SetDeployFolderCommand extends ServerWorkingCopyPropertyCommand { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] ServerWorkingCopyPropertyCommand cannot be resolved to a type > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[331] > [ERROR] public class SetOverrideCommand extends ServerWorkingCopyPropertyButtonCommand { > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] ServerWorkingCopyPropertyButtonCommand cannot be resolved to a type > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[339] > [ERROR] protected void postOp(int type) { > [ERROR] ^^^^^^^^^^^^^^^^ > [ERROR] The method postOp(int) of type OpenShiftServerEditorSection.SetOverrideCommand must override or implement a supertype method > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerWizardComposite.java:[273] > [ERROR] browseDeployFolderButton.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, null, 0, 100, 0)); > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes > [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerWizardComposite.java:[277] > [ERROR] deployFolderText.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, 0, 0, browseDeployFolderButton, -5)); > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes > [ERROR] 17 problems (17 errors) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
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 April 2014