[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:
------------------------------------
Please link to the job where you're seeing this failure. I'm not psychic, guys. :D
> 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-24676) CDK3 server adapter's console view is using wrong coding on all platforms
by Budh Ram Gurung (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ]
Budh Ram Gurung commented on JBIDE-24676:
-----------------------------------------
We are now looking for a simple solution of showing dots as progress instead of external package wheel. This should work with eclipse terminal emulator as well since not control characters are used for this approach.
[~rob.stryker][~mmalina] Let us know your opinion as well.
The logs will look like:
{code}
$ minishift start --username bgurung(a)redhat.com --password '*****' --iso-url file:///home/budhram/cache/iso/minishift-rhel7.iso
-- Checking if KVM driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
Checking driver binary is executable ... OK
-- Starting local OpenShift cluster using 'kvm' hypervisor ...
-- Minishift VM will be configured with ...
Memory: 2 GB
vCPUs : 2
Disk size: 20 GB
-- Starting Minishift VM ............ OK
-- Registering machine using subscription-manager ............... OK [1m0s]
-- Checking for IP address ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 1% OK
-- OpenShift cluster will be configured with ...
Version: v3.6.0
-- Checking `oc` support for startup flags ...
routing-suffix ... OK
host-config-dir ... OK
host-data-dir ... OK
host-pv-dir ... OK
host-volumes-dir ... OK
Starting OpenShift using openshift/origin:v3.6.0 ...
Pulling image openshift/origin:v3.6.0
[...]
{code}
> CDK3 server adapter's console view is using wrong coding on all platforms
> -------------------------------------------------------------------------
>
> Key: JBIDE-24676
> URL: https://issues.jboss.org/browse/JBIDE-24676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.5.0.AM2
> Environment: Windows, Linux, macOS
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: Console_output.png, cdk_console_coding.png, dot_spinner_error.png, no_progressbar.png, progress-win.PNG, progress.png
>
>
> Console view on all platforms show strange characters. See the pic.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24676) CDK3 server adapter's console view is using wrong coding on all platforms
by Budh Ram Gurung (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24676?page=com.atlassian.jira.plugi... ]
Budh Ram Gurung edited comment on JBIDE-24676 at 9/4/17 1:27 PM:
-----------------------------------------------------------------
We are now looking for a simple solution of showing dots as progress instead of external package wheel. This should work with eclipse terminal emulator as well since not control characters are used for this approach.
[~rob.stryker][~mmalina] Let us know your opinion as well.
The logs will look like:
{code}
$ minishift start --username bgurung(a)redhat.com --password '*****' --iso-url file:///home/budhram/cache/iso/minishift-rhel7.iso
-- Checking if KVM driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
Checking driver binary is executable ... OK
-- Starting local OpenShift cluster using 'kvm' hypervisor ...
-- Minishift VM will be configured with ...
Memory: 2 GB
vCPUs : 2
Disk size: 20 GB
-- Starting Minishift VM ............ OK
-- Registering machine using subscription-manager ............... OK [1m0s]
-- Checking for IP address ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 1% OK
-- OpenShift cluster will be configured with ...
Version: v3.6.0
-- Checking `oc` support for startup flags ...
routing-suffix ... OK
host-config-dir ... OK
host-data-dir ... OK
host-pv-dir ... OK
host-volumes-dir ... OK
Starting OpenShift using openshift/origin:v3.6.0 ...
Pulling image openshift/origin:v3.6.0
[...]
{code}
Pull request here - https://github.com/minishift/minishift/pull/1340.
was (Author: budhrg):
We are now looking for a simple solution of showing dots as progress instead of external package wheel. This should work with eclipse terminal emulator as well since not control characters are used for this approach.
[~rob.stryker][~mmalina] Let us know your opinion as well.
The logs will look like:
{code}
$ minishift start --username bgurung(a)redhat.com --password '*****' --iso-url file:///home/budhram/cache/iso/minishift-rhel7.iso
-- Checking if KVM driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
Checking driver binary is executable ... OK
-- Starting local OpenShift cluster using 'kvm' hypervisor ...
-- Minishift VM will be configured with ...
Memory: 2 GB
vCPUs : 2
Disk size: 20 GB
-- Starting Minishift VM ............ OK
-- Registering machine using subscription-manager ............... OK [1m0s]
-- Checking for IP address ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 1% OK
-- OpenShift cluster will be configured with ...
Version: v3.6.0
-- Checking `oc` support for startup flags ...
routing-suffix ... OK
host-config-dir ... OK
host-data-dir ... OK
host-pv-dir ... OK
host-volumes-dir ... OK
Starting OpenShift using openshift/origin:v3.6.0 ...
Pulling image openshift/origin:v3.6.0
[...]
{code}
> CDK3 server adapter's console view is using wrong coding on all platforms
> -------------------------------------------------------------------------
>
> Key: JBIDE-24676
> URL: https://issues.jboss.org/browse/JBIDE-24676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.5.0.AM2
> Environment: Windows, Linux, macOS
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: Console_output.png, cdk_console_coding.png, dot_spinner_error.png, no_progressbar.png, progress-win.PNG, progress.png
>
>
> Console view on all platforms show strange characters. See the pic.
--
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 Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-24966:
---------------------------------------
[~jjohnstn] can you please look at this change https://git.eclipse.org/r/#/c/104269/ ?
> 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:
> {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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4532:
----------------------------------
TODO:
* build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji
* build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji
* update jbt/devstudio TP to use these newer versions:
** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973
** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4532
> URL: https://issues.jboss.org/browse/JBDS-4532
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM1
> Reporter: Nick Boldt
>
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4532) RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4532?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4532 at 9/4/17 12:40 PM:
-----------------------------------------------------------
TODO:
* update jbt/devstudio TP to use these newer versions:
** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973
** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974
* build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji -> BZ?
* build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji -> BZ?
was (Author: nickboldt):
TODO:
* build org.jboss.tools.maven.apt.feature 1.3.0 (or newer) in Koji
* build org.jboss.tools.maven.sourcelookup.feature 1.8.101.v20170822-1709 (or newer) in Koji
* update jbt/devstudio TP to use these newer versions:
** org.eclipse.m2e.feature, org.eclipse.m2e.tests.common, org.eclipse.m2e.importer 0.8.0 -> JBIDE-24973
** org.sonatype.tycho.m2e.feature 0.9.0 -> JBIDE-24974
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4532
> URL: https://issues.jboss.org/browse/JBDS-4532
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: 3rd-party-dependencies, rpm, target-platform, upstream
> Affects Versions: 11.1.0.AM1
> Reporter: Nick Boldt
>
> RPM should depend on upstream m2e rpms, including apt, buildhelper, egit, mavenarchiver, maven importer, sourcelookup, & tycho. Depends on getting this done in Fedora and devtools channel first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months