[JBoss JIRA] (JBDS-3867) CDK file name should include version, match file name on RHCP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3867?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3867:
--------------------------------
Sprint: devex #126 January 2017
> CDK file name should include version, match file name on RHCP
> -------------------------------------------------------------
>
> Key: JBDS-3867
> URL: https://issues.jboss.org/browse/JBDS-3867
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.3.0.AM2
>
>
> The platform installer uses a file name for the CDK box with no version information making it difficult to tell if you have the latest CDK box or not.
> The downloaded box file is saved in \cdk\boxes\rhel-vagrant-virtualbox.box.
> It should use the same file name as the Red Hat Customer Portal to make it easy to identify that it is the same file: rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-virtualbox.box
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23738) create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23738?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23738 at 1/13/17 12:28 PM:
--------------------------------------------------------------
After the first pass - https://github.com/jbdevstudio/jbdevstudio-product/pull/441/files - I'm hitting this problem:
{code}
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.pde.api.tools.ui [206]
Unresolved requirement: Require-Bundle: org.eclipse.pde.api.tools; bundle-version="1.0.600"
-> Bundle-SymbolicName: org.eclipse.pde.api.tools; bundle-version="1.1.1.v20160920-1429"; singleton:="true"
org.eclipse.pde.api.tools [191]
Unresolved requirement: Require-Bundle: org.objectweb.asm; bundle-version="[5.0.1,6.0.0)"
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss OpenShift 3 Tools 3.3.2.v20170106-0320 (org.jboss.tools.openshift.feature.feature.group 3.3.2.v20170106-0320)
Missing requirement: Equinox Provisioning Repository 2.3.200.v20160421-0324 (org.eclipse.equinox.p2.repository 2.3.200.v20160421-0324) requires 'package javax.crypto 0.0.0' but it could not be found
Cannot satisfy dependency:
From: Equinox Provisioning Artifact Repository Support 1.1.500.v20160419-0834 (org.eclipse.equinox.p2.artifact.repository 1.1.500.v20160419-0834)
To: package org.eclipse.equinox.internal.p2.persistence 0.0.0
Cannot satisfy dependency:
From: Equinox Provisioning UI Support 2.4.100.v20160419-0834 (org.eclipse.equinox.p2.ui 2.4.100.v20160419-0834)
To: package org.eclipse.equinox.internal.p2.artifact.repository 0.0.0
Cannot satisfy dependency:
From: Equinox Provisioning Discovery UI 1.0.201.v20160901-1335 (org.eclipse.equinox.p2.ui.discovery 1.0.201.v20160901-1335)
To: bundle org.eclipse.equinox.p2.ui 2.0.0
Cannot satisfy dependency:
From: m2e Marketplace 1.7.1.20161104-1805 (org.eclipse.m2e.discovery 1.7.1.20161104-1805)
To: bundle org.eclipse.equinox.p2.ui.discovery 0.0.0
Cannot satisfy dependency:
From: Maven POM XML Editor 1.7.1.20161104-1805 (org.eclipse.m2e.editor.xml 1.7.1.20161104-1805)
To: bundle org.eclipse.m2e.discovery [1.7.0,1.8.0)
Cannot satisfy dependency:
From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.1.20161104-1805 (org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805)
To: org.eclipse.m2e.editor.xml [1.7.1.20161104-1805]
Cannot satisfy dependency:
From: JBoss OpenShift 3 Tools 3.3.2.v20170106-0320 (org.jboss.tools.openshift.feature.feature.group 3.3.2.v20170106-0320)
To: org.eclipse.m2e.feature.feature.group 1.2.0.20120903-1050
{code}
was (Author: nickboldt):
After the first pass, I'm hitting this problem:
{code}
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.pde.api.tools.ui [206]
Unresolved requirement: Require-Bundle: org.eclipse.pde.api.tools; bundle-version="1.0.600"
-> Bundle-SymbolicName: org.eclipse.pde.api.tools; bundle-version="1.1.1.v20160920-1429"; singleton:="true"
org.eclipse.pde.api.tools [191]
Unresolved requirement: Require-Bundle: org.objectweb.asm; bundle-version="[5.0.1,6.0.0)"
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss OpenShift 3 Tools 3.3.2.v20170106-0320 (org.jboss.tools.openshift.feature.feature.group 3.3.2.v20170106-0320)
Missing requirement: Equinox Provisioning Repository 2.3.200.v20160421-0324 (org.eclipse.equinox.p2.repository 2.3.200.v20160421-0324) requires 'package javax.crypto 0.0.0' but it could not be found
Cannot satisfy dependency:
From: Equinox Provisioning Artifact Repository Support 1.1.500.v20160419-0834 (org.eclipse.equinox.p2.artifact.repository 1.1.500.v20160419-0834)
To: package org.eclipse.equinox.internal.p2.persistence 0.0.0
Cannot satisfy dependency:
From: Equinox Provisioning UI Support 2.4.100.v20160419-0834 (org.eclipse.equinox.p2.ui 2.4.100.v20160419-0834)
To: package org.eclipse.equinox.internal.p2.artifact.repository 0.0.0
Cannot satisfy dependency:
From: Equinox Provisioning Discovery UI 1.0.201.v20160901-1335 (org.eclipse.equinox.p2.ui.discovery 1.0.201.v20160901-1335)
To: bundle org.eclipse.equinox.p2.ui 2.0.0
Cannot satisfy dependency:
From: m2e Marketplace 1.7.1.20161104-1805 (org.eclipse.m2e.discovery 1.7.1.20161104-1805)
To: bundle org.eclipse.equinox.p2.ui.discovery 0.0.0
Cannot satisfy dependency:
From: Maven POM XML Editor 1.7.1.20161104-1805 (org.eclipse.m2e.editor.xml 1.7.1.20161104-1805)
To: bundle org.eclipse.m2e.discovery [1.7.0,1.8.0)
Cannot satisfy dependency:
From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.1.20161104-1805 (org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805)
To: org.eclipse.m2e.editor.xml [1.7.1.20161104-1805]
Cannot satisfy dependency:
From: JBoss OpenShift 3 Tools 3.3.2.v20170106-0320 (org.jboss.tools.openshift.feature.feature.group 3.3.2.v20170106-0320)
To: org.eclipse.m2e.feature.feature.group 1.2.0.20120903-1050
{code}
> create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25)
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-23738
> URL: https://issues.jboss.org/browse/JBIDE-23738
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, rpm
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
>
> Per trello card [1], we should consider having a jbosstools rpm.
> Could put the source for this in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ or in jbdevstudio-product since it'll be a similar design to that one, including blacklists and dependencies.
> [1] https://trello.com/c/YK6rdGRy/14-create-jbosstools-rpm-for-fedora-24-25
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23738) create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23738?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23738:
------------------------------------
After the first pass, I'm hitting this problem:
{code}
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.pde.api.tools.ui [206]
Unresolved requirement: Require-Bundle: org.eclipse.pde.api.tools; bundle-version="1.0.600"
-> Bundle-SymbolicName: org.eclipse.pde.api.tools; bundle-version="1.1.1.v20160920-1429"; singleton:="true"
org.eclipse.pde.api.tools [191]
Unresolved requirement: Require-Bundle: org.objectweb.asm; bundle-version="[5.0.1,6.0.0)"
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss OpenShift 3 Tools 3.3.2.v20170106-0320 (org.jboss.tools.openshift.feature.feature.group 3.3.2.v20170106-0320)
Missing requirement: Equinox Provisioning Repository 2.3.200.v20160421-0324 (org.eclipse.equinox.p2.repository 2.3.200.v20160421-0324) requires 'package javax.crypto 0.0.0' but it could not be found
Cannot satisfy dependency:
From: Equinox Provisioning Artifact Repository Support 1.1.500.v20160419-0834 (org.eclipse.equinox.p2.artifact.repository 1.1.500.v20160419-0834)
To: package org.eclipse.equinox.internal.p2.persistence 0.0.0
Cannot satisfy dependency:
From: Equinox Provisioning UI Support 2.4.100.v20160419-0834 (org.eclipse.equinox.p2.ui 2.4.100.v20160419-0834)
To: package org.eclipse.equinox.internal.p2.artifact.repository 0.0.0
Cannot satisfy dependency:
From: Equinox Provisioning Discovery UI 1.0.201.v20160901-1335 (org.eclipse.equinox.p2.ui.discovery 1.0.201.v20160901-1335)
To: bundle org.eclipse.equinox.p2.ui 2.0.0
Cannot satisfy dependency:
From: m2e Marketplace 1.7.1.20161104-1805 (org.eclipse.m2e.discovery 1.7.1.20161104-1805)
To: bundle org.eclipse.equinox.p2.ui.discovery 0.0.0
Cannot satisfy dependency:
From: Maven POM XML Editor 1.7.1.20161104-1805 (org.eclipse.m2e.editor.xml 1.7.1.20161104-1805)
To: bundle org.eclipse.m2e.discovery [1.7.0,1.8.0)
Cannot satisfy dependency:
From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.7.1.20161104-1805 (org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805)
To: org.eclipse.m2e.editor.xml [1.7.1.20161104-1805]
Cannot satisfy dependency:
From: JBoss OpenShift 3 Tools 3.3.2.v20170106-0320 (org.jboss.tools.openshift.feature.feature.group 3.3.2.v20170106-0320)
To: org.eclipse.m2e.feature.feature.group 1.2.0.20120903-1050
{code}
> create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25)
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-23738
> URL: https://issues.jboss.org/browse/JBIDE-23738
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, rpm
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
>
> Per trello card [1], we should consider having a jbosstools rpm.
> Could put the source for this in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ or in jbdevstudio-product since it'll be a similar design to that one, including blacklists and dependencies.
> [1] https://trello.com/c/YK6rdGRy/14-create-jbosstools-rpm-for-fedora-24-25
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4248) Uninstaller script asks to press any key to exit, but accepts only Enter
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4248?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4248:
--------------------------------
Fix Version/s: 10.3.0.AM2
> Uninstaller script asks to press any key to exit, but accepts only Enter
> ------------------------------------------------------------------------
>
> Key: JBDS-4248
> URL: https://issues.jboss.org/browse/JBDS-4248
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Environment: Windows
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> Uninstaller PS script asks to press any key to exit
> {code}PS C:\Users\eskimo> powershell -ExecutionPolicy bypass -file C:\DevelopmentSuite1\uninstaller\uninstall.ps1
> Uninstalling Red Hat Development Suite
> Removing installation folder
> DONE
> Removing path entries
> DONE
> Press any key to exit
> {code}
> But it exits only when Enter pressed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23291?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-23291 at 1/13/17 9:58 AM:
------------------------------------------------------------------
I don't think that we can say that it is "as expected", it is "as designed" but we have a functional issue here. The status is "started, synchronized" although the CDK server is not available.
What is "expected" is that the status is "synchronizing" and/or when the timeout ends, some kind of "error" on connection.
Just looking for the vagrant status seems not enough.
was (Author: aurelien.pupier):
I don't think that we can say that it is "as expected", it is "as designed" but we have a functional issue here. The status is "started, synchronized" although the CDK server is not available.
What is "expected" is that the status is "synchronizing" and/or when the timeout ends, some kind of "error" on connection.
> If start of container fails on timeout, the status in server view is "Started, Synchronized"
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23291
> URL: https://issues.jboss.org/browse/JBIDE-23291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.2.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months