[JBoss JIRA] Created: (JBDS-1047) JBDS 3.0 CR1, can a check be made when running from the command line to install as root
by Jim Tyrrell (JIRA)
JBDS 3.0 CR1, can a check be made when running from the command line to install as root
---------------------------------------------------------------------------------------
Key: JBDS-1047
URL: https://jira.jboss.org/jira/browse/JBDS-1047
Project: JBoss Developer Studio
Issue Type: Feature Request
Components: installer
Environment: Linux JDK 6
Reporter: Jim Tyrrell
When I ran the installer I was not paying attention and ran it as root, it ended up installed in /usr/local/jbdevstudio3cr1. I then tried to run the uninstaller and was left with a few items in the Applications -> Programming Main menu as seen in the attached screen shot. Should we check to see if you are trying to install as root on linux. It also seemed that I was not able to have any servers available in the server view, although I am not sure if that is a first time running the cr1 installer error as seemed to have happened on my mac, where I never run as root. Now that I have installed once there is no way to test this hypothesis.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBDS-1088) Make installer complain more strongly about installing over old verions
by James Livingston (JIRA)
Make installer complain more strongly about installing over old verions
-----------------------------------------------------------------------
Key: JBDS-1088
URL: https://jira.jboss.org/jira/browse/JBDS-1088
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 2.1.1
Reporter: James Livingston
If you have a copy of, for example, JBDS 2.0.0 installed to /opt/jbds and then try to install 2.1.0 to that location it gives you the "Are you sure you want to overwrite that folder" warning, the same as for any existing directory.
It would be good if it detected that there was an older copy of JBDS installed to that location, and gave you a stronger "You can't upgrade by installing over the top" warning. Installing 2.1.0 over the top of 2.0.0 leaves you with a mixed up installation, with some versions of plugins from the old version and some from the new version.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBIDE-5143) ClassCastException when create f:selectItem inside h:selectManyListBox
by Yura Zhishko (JIRA)
ClassCastException when create f:selectItem inside h:selectManyListBox
----------------------------------------------------------------------
Key: JBIDE-5143
URL: https://jira.jboss.org/jira/browse/JBIDE-5143
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.1.0.M4
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
Priority: Minor
1) Open attached page with VPE.
2) Find any line that contains f:selectItem and comment it.
RESULT: During visual DOM building next exception occurs:
java.lang.ClassCastException: $Proxy26
at org.jboss.tools.jsf.vpe.jsf.template.selectitem.AbstractSelectItemTemplate.processOutputAttribute(AbstractSelectItemTemplate.java:99)
at org.jboss.tools.jsf.vpe.jsf.template.selectitem.AbstractOptionSelectItemTemplate.create(AbstractOptionSelectItemTemplate.java:67)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:489)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:689)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:601)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:597)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:287)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:662)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:235)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.rebuildDom(VpeVisualDomBuilder.java:263)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:987)
at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:661)
at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:489)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
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:3855)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
--
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
16 years, 1 month