June 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6537) Helios support for JBT v3.1.1

by Darryl Miles (JIRA)

Helios support for JBT v3.1.1 ----------------------------- Key: JBIDE-6537 URL: https://jira.jboss.org/browse/JBIDE-6537 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate, Seam Affects Versions: 3.1.1 Reporter: Darryl Miles Assignee: Max Rydahl Andersen Both the "Hibernate Tools" and "Seam Tools" for JBT v3.1.1 have too narrow version requirements for com.ibm.icu to be compatible with Helios. Helios comes with com.ibm.icu v4.2.1 Currently the version requirements are set to [3.4.4,4.1.0) so this should be changed at a minimum to [3.4.4,4.3.0) to allow both these JBT components to install on top of Helios. However you should consider using an even wider version width of [3.4.4,5) since it is accepted practise that minor version increments are backwardly compatible and a major version change is potentially API breaking. This means that generally JBT should (and is expected to) work on all future versions of com.ibm.icu up until version 5 is released. -- 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

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9206) AS7 Adapter : Deployment of zipped projects fail if the temporary folder doesn't exist

by Fred Bricon (JIRA)

AS7 Adapter : Deployment of zipped projects fail if the temporary folder doesn't exist -------------------------------------------------------------------------------------- Key: JBIDE-9206 URL: https://issues.jboss.org/browse/JBIDE-9206 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Fred Bricon Assignee: Rob Stryker Fix For: 3.3.0.M3 I noticed that, in the context of JBIDE-9133, for the existing -broken- AS7 server instances the utility projects were not zipped to the deployment area. On the other hand, creating a new server instance fixed the issue. So it seems the temporary folder is only created at the same time as the server instance. It's an issue in the sense that you can not guarantee the temporary folder will exist at deployment time (could have been deleted by the user ...). Solution is to call tempdir.mkdirs() right before the actual deployment occurs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1679) Deadlock issue when creating a JSF portlet

by Thomas Heute (JIRA)

Deadlock issue when creating a JSF portlet ------------------------------------------ Key: JBDS-1679 URL: https://issues.jboss.org/browse/JBDS-1679 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.GA Environment: Fedora 15, OpenJDK OpenJDK Runtime Environment (IcedTea6 1.10.1) (fedora-57.1.10.1.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Reporter: Thomas Heute Attachments: jsfPortlet.txt I tried to create a JSF Portlet project (Facet enabled where JSF 1.2, Core Portlet, JSF/Seam Portlet), and then default options for an EPP target runtime. The creation of the project gets stuck "Installing JSF Facet", I'll attach the jstack result that shows a deadlock. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
17
0 / 0

[JBoss JIRA] Created: (JBDS-1474) List of update sites is extended after first update with eclipse update sites

by Denis Golovin (JIRA)

List of update sites is extended after first update with eclipse update sites ----------------------------------------------------------------------------- Key: JBDS-1474 URL: https://issues.jboss.org/browse/JBDS-1474 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8338) Seam Components View ignores Filter settings for view

by Denis Golovin (JIRA)

Seam Components View ignores Filter settings for view ----------------------------------------------------- Key: JBIDE-8338 URL: https://issues.jboss.org/browse/JBIDE-8338 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.CR2 (tentative) Reporter: Denis Golovin Assignee: Alexey Kazakov Attachments: Screenshot.png -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8980) fix RealmMockIntegrationTest#canGetProfile

by Andre Dietisheim (JIRA)

fix RealmMockIntegrationTest#canGetProfile ------------------------------------------ Key: JBIDE-8980 URL: https://issues.jboss.org/browse/JBIDE-8980 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 3.3.0.M2 Currently RealmMockIntegrationTest#canGetProfile fails. It shall get fixed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9232) JBoss 7: JSF 2 apps stop working

by Juergen Zimmermann (JIRA)

JBoss 7: JSF 2 apps stop working -------------------------------- Key: JBIDE-9232 URL: https://issues.jboss.org/browse/JBIDE-9232 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Juergen Zimmermann Assignee: Rob Stryker I'm using JBossTools 3.3_stable_branch.aggregate-Update-2011-06-18_05-30-41-H2. Now I tried the latest Jenkins Build 1267 of JBoss 7 and I'm getting a classpath issue regarding JSF 2: JBoss Tools is including * jsf-api-1.2_13.jar from modules/javax/faces/api/1.2 * jboss-jsf-api_2.0_spec-1.0.0.Final.jar from modules/javax/faces/api/main It looks like the 1.2 stuff is included earlier in the classpath, so that e.g. ExternalContext.getFlash(), ExternalContext.invalidateSession() or Application.createComponent(FacesContext,String,String) are not available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8008) SeamProjectNewWizardTest.testJiraJbide1111 failure

by Alexey Kazakov (JIRA)

SeamProjectNewWizardTest.testJiraJbide1111 failure -------------------------------------------------- Key: JBIDE-8008 URL: https://issues.jboss.org/browse/JBIDE-8008 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Alexey Kazakov junit.framework.AssertionFailedError: Finish button is disabled at first wizard page in spite of created JBoss AS Runtime, Server, DB Connection and Seam Runtime and valid project name. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.wizard.SeamProjectNewWizardTest.testJiraJbide1111(SeamProjectNewWizardTest.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116) 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:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9278) Conflicting dependency prevents installation of JBoss Tools for Eclipse Indigo

by Rick Wagner (JIRA)

Conflicting dependency prevents installation of JBoss Tools for Eclipse Indigo ------------------------------------------------------------------------------ Key: JBIDE-9278 URL: https://issues.jboss.org/browse/JBIDE-9278 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M2 Environment: 64-bit Fedora, Eclipse 3.7 Reporter: Rick Wagner With a new download of eclipse-jee-indigo-M6a-linux-gtk-x86_64.tar.gz, I get the following message when trying to install All JBoss Tools 3.3. I'm following Max's latest blog about this combination, but the installation isn't working for me. Thanks! Cannot complete the install because of a conflicting dependency. > Software being installed: Runtime Initialization 1.3.0.v20110624-0453-H4-M2 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20110624-0453-H4-M2) > Software currently installed: Eclipse IDE for Java EE Developers 1.4.0.20110319-2300 (epp.package.jee 1.4.0.20110319-2300) > Only one of the following can be installed at once: > Common Navigator View 3.5.100.I20110524-0800 (org.eclipse.ui.navigator 3.5.100.I20110524-0800) > Common Navigator View 3.5.0.I20100601-0800 (org.eclipse.ui.navigator 3.5.0.I20100601-0800) > Common Navigator View 3.5.100.I20110519-0100 (org.eclipse.ui.navigator 3.5.100.I20110519-0100) > Cannot satisfy dependency: > From: Eclipse IDE for Java EE Developers 1.4.0.20110319-2300 (epp.package.jee 1.4.0.20110319-2300) > To: org.eclipse.epp.package.jee.feature.feature.group [1.4.0.20110319-2300] > Cannot satisfy dependency: > From: Java EE IDE Feature 1.4.0.20110319-2300 (org.eclipse.epp.package.jee.feature.feature.group 1.4.0.20110319-2300) > To: org.eclipse.platform.feature.group [3.7.0.r20110302-9gF7SHCIFt6ms-lIjrC6vK_XO-IabJMKu] > Cannot satisfy dependency: > From: Eclipse Platform 3.7.0.r20110302-9gF7SHCIFt6ms-lIjrC6vK_XO-IabJMKu (org.eclipse.platform.feature.group 3.7.0.r20110302-9gF7SHCIFt6ms-lIjrC6vK_XO-IabJMKu) > To: org.eclipse.ui.navigator [3.5.0.I20100601-0800] > Cannot satisfy dependency: > From: JBoss Runtime Initializer 1.3.0.v20110624-0453-H4-M2 (org.jboss.tools.runtime 1.3.0.v20110624-0453-H4-M2) > To: bundle org.eclipse.ui.navigator 3.5.100 > Cannot satisfy dependency: > From: Runtime Initialization 1.3.0.v20110624-0453-H4-M2 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20110624-0453-H4-M2) > To: org.jboss.tools.runtime [1.3.0.v20110624-0453-H4-M2] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear

by Aliaksey Nis (JIRA)

Warning related to incorrect Seam project name don't appear ----------------------------------------------------------- Key: JBIDE-5284 URL: https://jira.jboss.org/jira/browse/JBIDE-5284 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis Priority: Optional Attachments: NoWarningSeam.JPG Related to JBIDE-5223 EXECUTE: New Seam project. EXECUTE: Input name "blahblah+". EXECUTE: Press next few times. ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name. FAILURE: No warning appears. It appears only if you press Back, then Next again. Screenshot attached. -- 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

14 years, 9 months

7
10
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 June 2011