[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
by Isaac Rooskov (JIRA)
Isaac Rooskov created JBDS-2260:
-----------------------------------
Summary: Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
Key: JBDS-2260
URL: https://issues.jboss.org/browse/JBDS-2260
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 5.0.0.GA
Reporter: Isaac Rooskov
*From customer in Bugzilla*
Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793
Description of issue from customer:
Description of problem:
Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
Version-Release number of selected component (if applicable):
JBOSS Developer Studio 5.0.0.GA
How reproducible:
Start installation using
java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar
Actual results:
Installation is not passing at step 7 of 9, progress 1 of 4.
Expected results:
Additional info:
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-8973) Provide a way to convert pure java libs into maven provided dependencies
by Max Rydahl Andersen (JIRA)
Provide a way to convert pure java libs into maven provided dependencies
------------------------------------------------------------------------
Key: JBIDE-8973
URL: https://issues.jboss.org/browse/JBIDE-8973
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
Fix For: 3.3.0.M3
Execute: multiple select lib dependencies, then right click and choose "Build path > Convert to Maven dependencies"
Assert: UI is shown that shows which jars misses metadata and what can be automatically detected based on maven metadata in the jar. UI has option to delete jars from project.
Execute: Press Ok
Assert: The jars are removed from classpath container, and now available in the classpath container and if user chose to delete then the files are removed from the project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13129) Beans XML 1.0 Editor throws XModelException: Cdi beans beans.xml already contains Scan
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-13129:
-------------------------------------
Summary: Beans XML 1.0 Editor throws XModelException: Cdi beans beans.xml already contains Scan
Key: JBIDE-13129
URL: https://issues.jboss.org/browse/JBIDE-13129
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 4.0.0.CR1
Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121118-2035-B111.jar
Reporter: Daniel Azarov
Assignee: Alexey Kazakov
Test case
Execute:
1. Create CDI project
2. Open beans.xml in Beans XML 1.0 Editor
3. Select New->Weld->Scan... context menu on beans.xml node in Tree tab
4. Do it again
FAIL:
{code}
org.jboss.tools.common.model.XModelException: Cdi beans beans.xml already contains Scan.
at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:179)
at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:169)
at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:143)
at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.executeHandler(DefaultCreateHandler.java:49)
at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65)
at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:96)
at org.jboss.tools.common.model.ui.action.XModelObjectAction$AL.widgetSelected(XModelObjectAction.java:131)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
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:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
{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, 4 months
[JBoss JIRA] (JBIDE-13069) Could not find any files matching glob
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-13069:
-----------------------------------
Summary: Could not find any files matching glob
Key: JBIDE-13069
URL: https://issues.jboss.org/browse/JBIDE-13069
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Alpha2
Environment: Win 7 - 32-bit JDK 7
Reporter: Burr Sutter
Assignee: Andre Dietisheim
use of Tail Files via the server adapter or the openshift explorer result in
Could not find any files matching glob
--
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, 4 months
[JBoss JIRA] (JBIDE-13087) Can't embed RockMongo
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13087:
----------------------------------------
Summary: Can't embed RockMongo
Key: JBIDE-13087
URL: https://issues.jboss.org/browse/JBIDE-13087
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.0.0.CR1
The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
Additionally I'm unable to embed those cartridges. I can see the following error message.
Could not embed cartridges for application myphptesting
Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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, 4 months