[JBoss JIRA] (JBIDE-14818) there's no "deployments" page for OpenShift that would allow me to rename a module
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14818:
------------------------------------------
postponing since there's not enough time to have this fixed until we freeze Alpha1.
> there's no "deployments" page for OpenShift that would allow me to rename a module
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-14818
> URL: https://issues.jboss.org/browse/JBIDE-14818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
>
> In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15934:
--------------------------------------
This does happen on my test randomly as well. 48% is exactly when it calls adb to install. However in random cases adb install simply does not return. You can cancel that particular task on the progress view.
> Run on Android Device does not work on OS X
> -------------------------------------------
>
> Key: JBIDE-15934
> URL: https://issues.jboss.org/browse/JBIDE-15934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: OS X Mavericks
> Latest Android SDK
> JBDS 7.1.0.Beta1
> Nexus 7
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Fix For: 4.1.1.CR1
>
>
> Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device.
> This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.)
> When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux.
> I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed.
> We even tried to deploy the app using adb install and it worked (while the device was still connected)
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16044) Typo in OpenShift preferences: timeout > time out
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16044?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16044.
---------------------------------
Verified in JBDS 7.1.0.CR1
Build id: CR1-v20131124-0717-B560
> Typo in OpenShift preferences: timeout > time out
> -------------------------------------------------
>
> Key: JBIDE-16044
> URL: https://issues.jboss.org/browse/JBIDE-16044
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Andre Dietisheim
> Priority: Trivial
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> Click Window > Preferences > JBoss Tools > OpenShift.
> 'Remote requests timeout ...' should be 'Remote requests *time out* ...'
> Within Red Hat content services we follow the IBM style guide. It states that it should be spelled as two words "time out".
--
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
12 years, 4 months
[JBoss JIRA] (JBDS-2833) CLONE - Installer fails due to spaces in JDK path on Windows 8
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2833?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-2833:
----------------------------------
Hi Denis, please resolve this issue. I know that the fix is in master already. I cannot resolve, because of insufficient privileges. Thanks.
> CLONE - Installer fails due to spaces in JDK path on Windows 8
> --------------------------------------------------------------
>
> Key: JBDS-2833
> URL: https://issues.jboss.org/browse/JBDS-2833
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Pavol Srna
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.Alpha1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{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
12 years, 4 months
[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15934:
---------------------------------------
OK, I installed build tools. And then I tried to use Run on Android Device again. This time, the progress is stuck at 48 % on Launching myhybridproj (Android Device) Launching: Launching delegate...
And it won't move.
I tried again the same and with the same result - progress stuck at 48 %.
> Run on Android Device does not work on OS X
> -------------------------------------------
>
> Key: JBIDE-15934
> URL: https://issues.jboss.org/browse/JBIDE-15934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: OS X Mavericks
> Latest Android SDK
> JBDS 7.1.0.Beta1
> Nexus 7
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Fix For: 4.1.1.CR1
>
>
> Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device.
> This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.)
> When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux.
> I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed.
> We even tried to deploy the app using adb install and it worked (while the device was still connected)
--
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
12 years, 4 months