[JBoss JIRA] (JBIDE-24968) VersionProviderTest.testFallBackEmbeddedValues is failing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24968?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24968:
------------------------------------
LOL, you should look here for a few failing jobs: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> VersionProviderTest.testFallBackEmbeddedValues is failing
> ---------------------------------------------------------
>
> Key: JBIDE-24968
> URL: https://issues.jboss.org/browse/JBIDE-24968
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.5.1.AM1
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Critical
>
> the test if failing since the beginning of August.
> It seems that the test was not played before, see [JBIDE-19081] so maybe it is that it has never worked
> {noformat}
> Error Message
> ide-config.properties can't be loaded from the org.jboss.tools.foundation.core plugin
> Stacktrace
> java.lang.RuntimeException: ide-config.properties can't be loaded from the org.jboss.tools.foundation.core plugin
> at java.util.Properties$LineReader.readLine(Properties.java:434)
> at java.util.Properties.load0(Properties.java:353)
> at java.util.Properties.load(Properties.java:341)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getProperties(VersionPropertiesProvider.java:293)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadDefaultProperties(VersionPropertiesProvider.java:204)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:158)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:217)
> at org.jboss.tools.foundation.core.properties.internal.VersionProviderTest.testFallBackEmbeddedValues(VersionProviderTest.java:207)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ]
Jeff Johnston commented on JBIDE-24966:
---------------------------------------
Patch is complete and part of Linux Tools Oxygen.1 RC3 and will soon be part of updates-nightly from master repo. I have merged a number of changes from Josef in with my patch. Assigning back to Nick Boldt.
> linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
> ------------------------------------------------------------------------------
>
> Key: JBIDE-24966
> URL: https://issues.jboss.org/browse/JBIDE-24966
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Jeff Johnston
> Priority: Blocker
> Fix For: 4.5.1.AM2
>
>
> Turns out we have a blocker here.
> org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace.
> Therefore this manifest needs to be changed, if we want to include Red Deer 2.0 in jbosstools 4.5.1.AM2 / devstudio 11.1.0.AM2:
> {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF}
> Require-Bundle: org.junit,org.eclipse.swt,
> org.eclipse.ui,
> org.eclipse.osgi,org.eclipse.core.runtime,
> org.jboss.reddeer.eclipse;bundle-version="1.2.1", <<
> org.jboss.reddeer.common;bundle-version="1.2.1", <<
> org.jboss.reddeer.swt;bundle-version="1.2.1", <<
> org.jboss.reddeer.core;bundle-version="1.2.1", <<
> org.jboss.reddeer.workbench;bundle-version="1.2.1", <<
> org.apache.commons.lang;bundle-version="2.6.0",
> org.eclipse.linuxtools.docker.core,
> org.hamcrest.library;bundle-version="1.3.0",
> org.hamcrest.core;bundle-version="1.3.0"{code}
> Note that the target platform freeze for the upcoming AM2 milestone is next Tuesday, Sept 12. Ideally, this would be fixed a few days before, so that I can apply other changes in advance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ]
Jeff Johnston reassigned JBIDE-24966:
-------------------------------------
Assignee: Nick Boldt (was: Jeff Johnston)
> linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2
> ------------------------------------------------------------------------------
>
> Key: JBIDE-24966
> URL: https://issues.jboss.org/browse/JBIDE-24966
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.5.1.AM2
>
>
> Turns out we have a blocker here.
> org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace.
> Therefore this manifest needs to be changed, if we want to include Red Deer 2.0 in jbosstools 4.5.1.AM2 / devstudio 11.1.0.AM2:
> {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF}
> Require-Bundle: org.junit,org.eclipse.swt,
> org.eclipse.ui,
> org.eclipse.osgi,org.eclipse.core.runtime,
> org.jboss.reddeer.eclipse;bundle-version="1.2.1", <<
> org.jboss.reddeer.common;bundle-version="1.2.1", <<
> org.jboss.reddeer.swt;bundle-version="1.2.1", <<
> org.jboss.reddeer.core;bundle-version="1.2.1", <<
> org.jboss.reddeer.workbench;bundle-version="1.2.1", <<
> org.apache.commons.lang;bundle-version="2.6.0",
> org.eclipse.linuxtools.docker.core,
> org.hamcrest.library;bundle-version="1.3.0",
> org.hamcrest.core;bundle-version="1.3.0"{code}
> Note that the target platform freeze for the upcoming AM2 milestone is next Tuesday, Sept 12. Ideally, this would be fixed a few days before, so that I can apply other changes in advance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24935) CDK3 server adapter: improve error message if it fails bcs no minishift location was set
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24935?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-24935.
---------------------------------
Resolution: Done
pushed
> CDK3 server adapter: improve error message if it fails bcs no minishift location was set
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-24935
> URL: https://issues.jboss.org/browse/JBIDE-24935
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.5.1.AM1
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: cdk3-server-adapter-failed-to-start-credentials.png, cdk3-server-adapter-failed-to-start.png
>
>
> # ASSERT: make sure that you have a cdk3/minishift-server adapter which is missing the "Minishift Binary" location.
> # EXEC: launch the server adapter
> Result:
> Server adapter fails to start, which is expected. But then the error message talks about the env vars missing the minishift binary. How would I as a dumb user know that I need to correct/set it in the server editor? IMHO we should tell so in the error message.
> !cdk3-server-adapter-failed-to-start.png!
> btw. if the username is missing, the error message tells me to open up the server editor, which tells the dump user what exactly to do.
> !cdk3-server-adapter-failed-to-start-credentials.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months