[JBoss JIRA] (JBIDE-20331) install grinder fails due to oomph or beaker virt slaves?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20331:
-------------------------------
Fix Version/s: 4.3.x
4.4.0.Alpha1
(was: 4.3.0.Final)
> install grinder fails due to oomph or beaker virt slaves?
> ---------------------------------------------------------
>
> Key: JBIDE-20331
> URL: https://issues.jboss.org/browse/JBIDE-20331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.x, 4.4.0.Alpha1
>
> Attachments: install-grinder-fail.txt, virt1-ftl.png, virt2-ftl.png
>
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull}
> 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20847) Only "retrieve" and "sign up here" link inside styled text should be accessible
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20847:
-------------------------------------
Summary: Only "retrieve" and "sign up here" link inside styled text should be accessible
Key: JBIDE-20847
URL: https://issues.jboss.org/browse/JBIDE-20847
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.CR2
Reporter: Marián Labuda
Priority: Minor
In New Connection dialog are 2 styled texts with links.
First one is for OpenShift 2 server selection on top saying "If you do not have an account on OpenShift, please +sign up here+."
Second one is for OpenShift 3 while OAuth authentication protocol is selected "Enter a token or +retrieve+ a new one."
Issue is that both are clickable whole, not just the underlined parts.
Issue is also differences while mouse cursor is moving over them. Second one, about a token, has hand cursor while mouse is over the text. First one has typical cursor for text. The cursor could be:
- for clickable part hand cursor
- for nonclickable part arrow cursor
Example of nice working text with link is link for OpenShift 3 server on top of wizard "New to OpenShift 3? Explore the +getting started documentation+."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20760:
-----------------------------------
Labels: respin-a (was: respin-a xtriage)
> docker feature not included in Marketplace entry for JBoss Tools
> ----------------------------------------------------------------
>
> Key: JBIDE-20760
> URL: https://issues.jboss.org/browse/JBIDE-20760
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.3.0.CR2
>
> Attachments: 20760.png
>
>
> Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry.
> Solution:
> 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?).
> 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2).
> Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace).
> Sound good?
> Alternative solutions:
> a. Create a new feature wrapper, just to contain the docker plugins
> b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin
> c. do nothing
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-20760:
---------------------------------
Labels: respin-a xtriage (was: xtriage)
> docker feature not included in Marketplace entry for JBoss Tools
> ----------------------------------------------------------------
>
> Key: JBIDE-20760
> URL: https://issues.jboss.org/browse/JBIDE-20760
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a, xtriage
> Fix For: 4.3.0.CR2
>
> Attachments: 20760.png
>
>
> Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry.
> Solution:
> 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?).
> 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2).
> Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace).
> Sound good?
> Alternative solutions:
> a. Create a new feature wrapper, just to contain the docker plugins
> b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin
> c. do nothing
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20760:
-------------------------------
Fix Version/s: 4.3.0.CR2
(was: 4.3.0.Final)
> docker feature not included in Marketplace entry for JBoss Tools
> ----------------------------------------------------------------
>
> Key: JBIDE-20760
> URL: https://issues.jboss.org/browse/JBIDE-20760
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a, xtriage
> Fix For: 4.3.0.CR2
>
> Attachments: 20760.png
>
>
> Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry.
> Solution:
> 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?).
> 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2).
> Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace).
> Sound good?
> Alternative solutions:
> a. Create a new feature wrapper, just to contain the docker plugins
> b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin
> c. do nothing
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-20803.
--------------------------------
Resolution: Done
No. You are not grokking it correctly. This set up can be used AS NEEDED against ANY URLs to facilitate updating the shared directory.xml files. I used it to pull the latest Alpha IS jars into the CR2 staging site. It doesn't touch the values in ide-config.properties
There is no immediate plan to automatically pull from the URLs in ide-config.properties. If that plan resurfaces for 4.3.x, it's in JBIDE-20664, not this issue.
Marking resolved.
> script process for merging IS jars into JBT/JBDS discovery sites
> ----------------------------------------------------------------
>
> Key: JBIDE-20803
> URL: https://issues.jboss.org/browse/JBIDE-20803
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, discovery, integration-platform
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Final
>
>
> Need to document and script how to get the IS jars into the JBT/JBDS discovery sites.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plug... ]
Pavol Srna commented on TOOLSDOC-683:
-------------------------------------
I need to verify JBIDE-20836 in the final build. I'll comment here once QE receives the build.
> Rel notes for 4.3.0 should list supported Codova versions
> ---------------------------------------------------------
>
> Key: TOOLSDOC-683
> URL: https://issues.jboss.org/browse/TOOLSDOC-683
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 4.3.0.Final
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: Configurations, Supported
> Fix For: 4.3.0.Final
>
>
> Related to: JBIDE-20836
> The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TOOLSDOC-683) Rel notes for 4.3.0 should list supported Codova versions
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-683?page=com.atlassian.jira.plug... ]
Martin Malina edited comment on TOOLSDOC-683 at 10/1/15 9:08 AM:
-----------------------------------------------------------------
[~psrna], can you take a look and confirm this, please? Thanks!
Correction: This is actually fixed in the Final build (respin of CR2) (JBIDE-20836) and we don't have that build yet, so this will be verified once we receive the Final build. We should receive the build today.
was (Author: mmalina):
[~psrna], can you take a look and confirm this, please? Thanks!
Correction: This is actually fixed in the Final build (respin of CR2) (JBIDE-20836) and we don't have that build yet, so this will be verified once we receive the Final build.
> Rel notes for 4.3.0 should list supported Codova versions
> ---------------------------------------------------------
>
> Key: TOOLSDOC-683
> URL: https://issues.jboss.org/browse/TOOLSDOC-683
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 4.3.0.Final
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: Configurations, Supported
> Fix For: 4.3.0.Final
>
>
> Related to: JBIDE-20836
> The issue is that given the frequency of Cordova releases, we cannot guarantee that we can always support the very latest release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20331) install grinder fails due to oomph or beaker virt slaves?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20331:
------------------------------------
[~mickael_istria] Can you branch https://github.com/jbosstools/jbosstools-install-grinder/ to 4.3.x? Then I think we can close this issue or slip it to 4.4.x.
> install grinder fails due to oomph or beaker virt slaves?
> ---------------------------------------------------------
>
> Key: JBIDE-20331
> URL: https://issues.jboss.org/browse/JBIDE-20331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Final
>
> Attachments: install-grinder-fail.txt, virt1-ftl.png, virt2-ftl.png
>
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull}
> 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months