October 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1844) Automated Installer Script Does Not Recored Preferred JRE

by Isaac Rooskov (JIRA)

Automated Installer Script Does Not Recored Preferred JRE --------------------------------------------------------- Key: JBDS-1844 URL: https://issues.jboss.org/browse/JBDS-1844 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 4.1.0.GA Reporter: Isaac Rooskov Priority: Critical Fix For: 4.1.1.Final ***Issue submitted by Will Dinyes through Bugzilla (Bug #736128)*** Description of problem: Automated installations of JBDS fail on Windows due to the preferred JRE location not being recorded by the graphical installer for reuse in cases where the preferred JRE is not also on the PATH. Version-Release number of selected component (if applicable): 4.1.0.GA How reproducible: Easily reproducible. Steps to Reproduce: 1. Install Java on Windows, but do not add to PATH (this simulates a Java install that is not in the user's PATH, such as a preferred Java version, or other Java setup) [or remove Java from the user's PATH]. 2. Run the graphical installer for JBDS 4.1, being sure to indicate the location of the JRE you wish to use to run JBDS. 3. Copy out the InstallConfigRecord.xml from the installed JBDS directory for use later. 4. Note: this file does not include any setting for the selected Java JRE that was used during the install. 5. Uninstall JBDS. 6. Re-install JBDS using the command java -jar jbdevstudio*.jar InstallConfigRecord.xml to run an automated install. 7. Attempt to start JBDS, and get an issue with a missing JRE, because said JRE is not on the PATH or in the JBDS install directory. Actual results: JBDS fails to start. Expected results: JBDS starts with the user-selected JRE. Additional info: Obviously, we can work around this by adding the JRE to the PATH on Windows, but we should be able to respect the installer's setting in the recorded script, rather than ignoring input from the user. I've set this to low priority. The same process works fine on vanilla Red Hat Enterprise Linux, presumably because the install of Java via RPM automatically adds the Java executables to a user's PATH (installs to /usr/bin, or the like). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
14
0 / 0

[JBoss JIRA] Created: (JBDS-1852) Wrong version displayed in Splash screen and About Box

by Vlado Pakan (JIRA)

Wrong version displayed in Splash screen and About Box ------------------------------------------------------ Key: JBDS-1852 URL: https://issues.jboss.org/browse/JBDS-1852 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: ui/branding Affects Versions: 4.1.1.M1 Environment: jbdevstudio-product-eap-linux-gtk-4.1.1.v201109080253R-H679-M1 Reporter: Vlado Pakan Priority: Critical Fix For: 4.1.1.M1 JBDS is displaying version 4.1.1.GA in Splashscreen and About Box. It has to be version 4.1.1.M1. Data from About box: Version: 4.1.1.GA Build id: v20110908-0132-H1012-GA Build date: 20110908-0132 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

8
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9770) JBDS 4.1.1 - creating a new ESB project - the highest numbered ESB runtime is 4.9 - should be 4.10

by Brian Fitzpatrick (JIRA)

JBDS 4.1.1 - creating a new ESB project - the highest numbered ESB runtime is 4.9 - should be 4.10 -------------------------------------------------------------------------------------------------- Key: JBIDE-9770 URL: https://issues.jboss.org/browse/JBIDE-9770 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.2.2.M1 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 3.2.2.M2 We need the ESB list to include 4.10 (clone of JBDS-1864) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9751) Duplicate "Source" menu in Eclipse menubar when the open editor is VPE and focus is in "Package Explorer"

by Vlado Pakan (JIRA)

Duplicate "Source" menu in Eclipse menubar when the open editor is VPE and focus is in "Package Explorer" --------------------------------------------------------------------------------------------------------- Key: JBIDE-9751 URL: https://issues.jboss.org/browse/JBIDE-9751 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Vlado Pakan Assignee: Denis Maliarevich Priority: Minor Fix For: 3.3.0.M3 The "Source" menu is duplicated when VPE is opened and the "Package Explorer" view is in focus. See attached screenshots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-9427) "JBoss Tools Editor might not fully work in project... add JSF capabilities?" dialog appears when it should not

by Yahor Radtsevich (JIRA)

"JBoss Tools Editor might not fully work in project... add JSF capabilities?" dialog appears when it should not --------------------------------------------------------------------------------------------------------------- Key: JBIDE-9427 URL: https://issues.jboss.org/browse/JBIDE-9427 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Yahor Radtsevich "JBoss Tools Editor might not fully work in project... add JSF capabilities?" dialog may appear for HTML projects where it is unnecessary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (JBDS-1833) Absent image in GettingStarted Guide

by Dmitry Geraskov (JIRA)

Absent image in GettingStarted Guide ------------------------------------ Key: JBDS-1833 URL: https://issues.jboss.org/browse/JBDS-1833 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: documentation Affects Versions: 5.0.0.M3 Reporter: Dmitry Geraskov Assignee: Isaac Rooskov Priority: Minor Fix For: 5.0.0.M3 Attachments: image.PNG 1. Install JBDS 2. On welcome screen press Getting Strted ->Getting Strated With JBDS 3. It seems should be some image in the doc, please see attached screenshot -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9812) org.jboss.tools.seam.ui.test.SeamUiAllTests failure

by Alexey Kazakov (JIRA)

org.jboss.tools.seam.ui.test.SeamUiAllTests failure --------------------------------------------------- Key: JBIDE-9812 URL: https://issues.jboss.org/browse/JBIDE-9812 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.2.2.M2 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.2.M2 Failing tests: >>> org.jboss.tools.seam.ui.test.SeamUiAllTests.testProjectNameWithSpaces 2.146 12 >>> org.jboss.tools.seam.ui.test.SeamUiAllTests.testProjectNameWithUnderlines 2.129 12 >>> org.jboss.tools.seam.ui.test.SeamUiAllTests.testProjectNameWithMinuses 2.12 12 >>> org.jboss.tools.seam.ui.test.SeamUiAllTests.testProjectNameWithMultipleDots 2.123 12 {code} Error Message Path for project must have only one segment. Stacktrace java.lang.IllegalArgumentException: Path for project must have only one segment. at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:183) at org.eclipse.jst.j2ee.web.project.facet.WebFacetInstallDataModelProvider.getDefaultProperty(WebFacetInstallDataModelProvider.java:69) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.getProperty(DataModelImpl.java:130) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.getStringProperty(DataModelImpl.java:153) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.setWidgetValue(DataModelSynchHelper.java:338) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.doSynchUIWithModel(DataModelSynchHelper.java:238) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.synchUIWithModel(DataModelSynchHelper.java:213) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.propertyChanged(DataModelSynchHelper.java:183) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:347) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:338) at org.eclipse.jst.j2ee.web.project.facet.WebFacetInstallDataModelProvider.propertySet(WebFacetInstallDataModelProvider.java:116) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:182) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172) at org.eclipse.wst.common.componentcore.datamodel.FacetProjectCreationDataModelProvider.propertySet(FacetProjectCreationDataModelProvider.java:318) at org.eclipse.jst.j2ee.project.facet.J2EEFacetProjectCreationDataModelProvider.propertySet(J2EEFacetProjectCreationDataModelProvider.java:135) at org.eclipse.jst.j2ee.internal.web.archive.operations.WebFacetProjectCreationDataModelProvider.propertySet(WebFacetProjectCreationDataModelProvider.java:75) at org.jboss.tools.seam.internal.core.project.facet.SeamFacetProjectCreationDataModelProvider.propertySet(SeamFacetProjectCreationDataModelProvider.java:121) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:182) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setStringProperty(DataModelImpl.java:201) at org.jboss.tools.seam.ui.test.wizard.PackageNamesTest.tearDown(PackageNamesTest.java:46) at junit.framework.TestCase.runBare(TestCase.java:140) 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.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.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25) 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:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27) 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:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8126) Manage Keys Dialog: should select keys and close dialog on double click

by Andre Dietisheim (JIRA)

Manage Keys Dialog: should select keys and close dialog on double click ----------------------------------------------------------------------- Key: JBIDE-8126 URL: https://issues.jboss.org/browse/JBIDE-8126 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.x -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8290) Delete hotkey should do nothing unless all selections are DeltaCloud objects (not instances)

by Rob Stryker (JIRA)

Delete hotkey should do nothing unless all selections are DeltaCloud objects (not instances) -------------------------------------------------------------------------------------------- Key: JBIDE-8290 URL: https://issues.jboss.org/browse/JBIDE-8290 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Rob Stryker Assignee: Andre Dietisheim Fix For: 3.2.1 I continually end up deleting my entire cloud by accident. I select a few instances, try to delete them (which is of course impossible), and quickly press enter, and then my entire cloud is removed. This is a big pain. It'd be better if the delete hotkey did nothing if the selection is not only DeltaCloud objects -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-1851) JBDS installer does NOT detect soa 5.2 version correctly

by Pavol Srna (JIRA)

JBDS installer does NOT detect soa 5.2 version correctly -------------------------------------------------------- Key: JBDS-1851 URL: https://issues.jboss.org/browse/JBDS-1851 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 4.1.1.M1 Environment: jbdevstudio-product-linux-gtk-4.1.1.v201109080253R-H679-M1 Reporter: Pavol Srna Assignee: Snjezana Peco Priority: Critical Fix For: 4.1.1.M1 Attachments: Screenshot-1.png, Screenshot.png Installer does NOT detect SOA-5.2 version correctly. See screenshots attached. If I search for runtimes within JBDS using JBossTools runtime detector (through Preferences ..) it recognizes SOA 5.2 runtime well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
9
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 2011