[JBoss JIRA] (JBDS-2663) Installer fails due to spaces in JDK path on Windows 8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2663?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2663:
--------------------------------
Fix Version/s: 8.0.0.Alpha1
> Installer fails due to spaces in JDK path on Windows 8
> ------------------------------------------------------
>
> Key: JBDS-2663
> URL: https://issues.jboss.org/browse/JBDS-2663
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Affects Versions: 7.0.0.Beta2
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 7.1.0.CR1, 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, 7 months
[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15830:
------------------------------------------
I'm on the finishing line for RC1, in quite a rush. I'll tackle this issue this week before releasing openshift-java-client 2.5.0 for JBT 4.1.1.RC1 (freezing this thursday).
> openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15830
> URL: https://issues.jboss.org/browse/JBIDE-15830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Brenton Leanhardt
> Assignee: Andre Dietisheim
> Labels: openshift-java-client
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin.
> In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling.
> You can see this for details:
> https://github.com/openshift/origin-server/blob/master/documentation/arch...
> In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45).
--
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, 7 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:
---------------------------------------
I tried to google and found this: http://stackoverflow.com/questions/7135999/adb-not-finding-my-device-phon...
But that does no help - it says that you add your device to an ini file in case it's not properly recognized. But that's not my case - in my case it is recognized, but then it seems as if our tooling breaks it.
> 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
> 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, 7 months
[JBoss JIRA] (JBIDE-15904) Test Cordova combinations
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15904:
---------------------------------------
Linking JBIDE-15935 - Android SDK not installed automatically on OS X
> Test Cordova combinations
> -------------------------
>
> Key: JBIDE-15904
> URL: https://issues.jboss.org/browse/JBIDE-15904
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Vlado Pakan
> Priority: Blocker
> Fix For: 4.1.1.CR1
>
>
> Use this jira to collect results from testing:
> 1)
> Run On Android Emulator. On windows, Linux and Mac (in that prio order).
>
> Run On Android Device: On windows, Linux and Mac (in that prio order)
>
> The more SDK version we cover the better with the above two. I do not think
> we can cover all so we should start with latest and make our way down.
>
> 2)
> Changes on the Run configurations for Run on Android...
>
> 3)
> Install Cordova Plugin:
>
> Offline, windows, Linux, Mac
>
> 4)
> Share project via git. Import existing project.
>
> 5)
> Export native platform project
>
> 6)
> Export Mobile Application
> windows, linux, mac
--
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, 7 months
[JBoss JIRA] (JBIDE-15935) Android SDK not installed automatically on OS X
by Martin Malina (JIRA)
Martin Malina created JBIDE-15935:
-------------------------------------
Summary: Android SDK not installed automatically on OS X
Key: JBIDE-15935
URL: https://issues.jboss.org/browse/JBIDE-15935
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.1.Beta1
Environment: JBDS 7.1.0.Beta1
OS X Mavericks
Reporter: Martin Malina
Fix For: 4.1.1.CR1
When I install android tools from central and then I restart the IDE as requested, I should be asked to automatically download and install Android SDK (I got word it works this way on Linux). I got nothing like that on OS X.
So I had to download and setup SDK manually.
--
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, 7 months
[JBoss JIRA] (JBIDE-15904) Test Cordova combinations
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15904:
---------------------------------------
Linking JBIDE-15934 - Run on Android Device does not work on OS X
> Test Cordova combinations
> -------------------------
>
> Key: JBIDE-15904
> URL: https://issues.jboss.org/browse/JBIDE-15904
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Vlado Pakan
> Priority: Blocker
> Fix For: 4.1.1.CR1
>
>
> Use this jira to collect results from testing:
> 1)
> Run On Android Emulator. On windows, Linux and Mac (in that prio order).
>
> Run On Android Device: On windows, Linux and Mac (in that prio order)
>
> The more SDK version we cover the better with the above two. I do not think
> we can cover all so we should start with latest and make our way down.
>
> 2)
> Changes on the Run configurations for Run on Android...
>
> 3)
> Install Cordova Plugin:
>
> Offline, windows, Linux, Mac
>
> 4)
> Share project via git. Import existing project.
>
> 5)
> Export native platform project
>
> 6)
> Export Mobile Application
> windows, linux, mac
--
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, 7 months
[JBoss JIRA] (JBIDE-15934) Run on Android Device does not work on OS X
by Martin Malina (JIRA)
Martin Malina created JBIDE-15934:
-------------------------------------
Summary: 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
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, 7 months