[JBoss JIRA] (JBIDE-15858) No supported modifying environment variables cause error
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15858:
----------------------------------
Assignee: Andre Dietisheim (was: Marián Labuda)
> No supported modifying environment variables cause error
> --------------------------------------------------------
>
> Key: JBIDE-15858
> URL: https://issues.jboss.org/browse/JBIDE-15858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Attachments: environment_variables.png
>
>
> If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
> Another one is show after attempt to add variable.
> Other "Processing environment variables..."
> Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 months
[JBoss JIRA] (JBIDE-15858) No supported modifying environment variables cause error
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-15858:
-------------------------------------
Summary: No supported modifying environment variables cause error
Key: JBIDE-15858
URL: https://issues.jboss.org/browse/JBIDE-15858
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.1.Beta1
Reporter: Marián Labuda
Priority: Critical
Attachments: environment_variables.png
If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
Another one is show after attempt to add variable.
Other "Processing environment variables..."
Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 months
[JBoss JIRA] (JBIDE-15858) No supported modifying environment variables cause error
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-15858:
----------------------------------
Attachment: environment_variables.png
> No supported modifying environment variables cause error
> --------------------------------------------------------
>
> Key: JBIDE-15858
> URL: https://issues.jboss.org/browse/JBIDE-15858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Priority: Critical
> Attachments: environment_variables.png
>
>
> If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..."
> Another one is show after attempt to add variable.
> Other "Processing environment variables..."
> Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion).
--
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, 5 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 edited comment on JBIDE-15830 at 11/5/13 7:47 AM:
-------------------------------------------------------------------
I forked and cloned the repo and then tried to build it which failed:
{code}
Running hudson.plugins.openshift.JenkinsIntegrationTestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.449 sec <<< FAILURE! - in hudson.plugins.openshift.JenkinsIntegrationTestSuite
warning(junit.framework.TestSuite$1) Time elapsed: 0.014 sec <<< FAILURE!
junit.framework.AssertionFailedError: No tests found in hudson.plugins.openshift.OpenShiftIntegrationTest
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at junit.framework.TestSuite$1.runTest(TestSuite.java:100)
Results :
Failed tests:
TestSuite$1.warning No tests found in hudson.plugins.openshift.OpenShiftIntegrationTest
{code}
Easy fixable, but still, is this expected?
IMHO we should have a test in jenkins plugin that asserts the useragent
was (Author: adietish):
I forked and cloned the repo and then tried to build it which failed:
{code}
Running hudson.plugins.openshift.JenkinsIntegrationTestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.449 sec <<< FAILURE! - in hudson.plugins.openshift.JenkinsIntegrationTestSuite
warning(junit.framework.TestSuite$1) Time elapsed: 0.014 sec <<< FAILURE!
junit.framework.AssertionFailedError: No tests found in hudson.plugins.openshift.OpenShiftIntegrationTest
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at junit.framework.TestSuite$1.runTest(TestSuite.java:100)
Results :
Failed tests:
TestSuite$1.warning No tests found in hudson.plugins.openshift.OpenShiftIntegrationTest
{code}
Easy fixable, but still, is this expected?
> 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
> 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, 5 months
[JBoss JIRA] (JBDS-2663) Installer fails due to spaces in JDK path on Windows 8
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2663?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-2663:
---------------------------------
Summary: Installer fails due to spaces in JDK path on Windows 8 (was: Installer cannot find unpack200.exe due to spaces in JDK path on Windows 8)
> 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
> Fix For: 7.1.0.CR1
>
>
> {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, 5 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 forked and cloned the repo and then tried to build it which failed:
{code}
Running hudson.plugins.openshift.JenkinsIntegrationTestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.449 sec <<< FAILURE! - in hudson.plugins.openshift.JenkinsIntegrationTestSuite
warning(junit.framework.TestSuite$1) Time elapsed: 0.014 sec <<< FAILURE!
junit.framework.AssertionFailedError: No tests found in hudson.plugins.openshift.OpenShiftIntegrationTest
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at junit.framework.TestSuite$1.runTest(TestSuite.java:100)
Results :
Failed tests:
TestSuite$1.warning No tests found in hudson.plugins.openshift.OpenShiftIntegrationTest
{code}
Easy fixable, but still, is this expected?
> 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
> 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, 5 months
[JBoss JIRA] (JBIDE-15853) plugins w/o test classes should not be set to packaging=eclipse-test-plugin
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15853?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15853:
---------------------------------------
+1, why not :) note that simply running mvn verify for the whole jbosstoos-integration-tests repo will still not really work currently, but at least this error will be gone. What I'd like to achieve is to run only a stable subset of tests by default and thus having something working when simply running mvn verify
> plugins w/o test classes should not be set to packaging=eclipse-test-plugin
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15853
> URL: https://issues.jboss.org/browse/JBIDE-15853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
>
> 4 plugins in jbosstools-integration-tests have no test classes, but are set via their pom to packaging type eclipse-test-plugin instead of eclipse-plugin.
> As a result, these four plugins fail to run tests and the resulting build is red.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integration-tests.aggregate_master/101/consoleFull}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.archives.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.common.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.reddeer: No tests found.
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.ws.reddeer: No tests found.
> {code}
> I propose that if these plugins are meant to be framework/API code, containing no actual JUnit tests to run, that their poms be changed as follows:
> {code}
> - <packaging>eclipse-test-plugin</packaging>
> + <packaging>eclipse-plugin</packaging>
> {code}
> And they be moved from
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te...
> into
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
--
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, 5 months
[JBoss JIRA] (JBDS-2757) Remove java 6 requirement of EAP from installer
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2757?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2757.
-------------------------------
This has been verified in Alpha2, but verified again with JBDS 7.1.0.Beta1b B493
> Remove java 6 requirement of EAP from installer
> -----------------------------------------------
>
> Key: JBDS-2757
> URL: https://issues.jboss.org/browse/JBDS-2757
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.Alpha1
> Environment: OS X Mountain Lion
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha2
>
> Attachments: ins-step-4.png, ins-step-5.png
>
>
> There are two strings I would like removed from the installer:
> Step 4
> Please note that JBoss EAP 6 requires Java 6 or higher.
> !ins-step-4.png!
> Step 5
> (Java 6 is required to run JBoss EAP 6)
> !ins-step-5.png!
> I think this was added when we still supported running of JBDS with Java 5, but now that JBDS needs Java 6 I think it's not needed to point this out explicitly.
> Also, in Step 4 there's this:
> JBoss Developer Studio works with Java 6 and has been tested with OpenJDK, Oracle and Apple JDK.
> - Here I would add Java 7 to the mix - we test that too.
> And last, EAP should be Red Hat JBoss Enterprise Application Platform (in Step 5).
--
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, 5 months
[JBoss JIRA] (JBIDE-15512) CordovaSim: need to implement InAppBrowser plugin
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15512?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15512:
-------------------------------------
[~maxandersen], yes you're right. We are going to include it in 4.1.x
Actually ChildBrowser is deprecated (http://community.phonegap.com/nitobi/topics/_childbrowser_plugin_deprecat... ) and inAppBrowser , which is part of the core API, is considered to be a substitution. However, ChildBrowser is one of the most popular plugins ever ( https://build.phonegap.com/plugins ). Furthermore ChildBrowser and InAppBrowser have very similar API. So, due to this similarity ChildBrowser's events are simply caught from js and handled just as InAppBrowser's events .
> CordovaSim: need to implement InAppBrowser plugin
> -------------------------------------------------
>
> Key: JBIDE-15512
> URL: https://issues.jboss.org/browse/JBIDE-15512
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> InAppBrowser ( http://docs.phonegap.com/en/3.0.0/cordova_inappbrowser_inappbrowser.md.ht... ) which is based on Child Browser plugin is part of org.apache.cordova API.
> This feature can't be implemented via iframe, because of the X-Frame-Options and Same-origin policy. So, it should be implemented via browserFunction (org.eclipse.swt.browser.BrowserFunction) and SWT Browser widget
--
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, 5 months