[JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20849:
----------------------------------
Labels: connection_wizard (was: )
> Blank space in a New Connection dialog
> --------------------------------------
>
> Key: JBIDE-20849
> URL: https://issues.jboss.org/browse/JBIDE-20849
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: connection_wizard
> Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png
>
>
> There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks.
> !openshift2_connection_dialog.png!
> !openshift3_connection_dialog.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20849:
-------------------------------------
Summary: Blank space in a New Connection dialog
Key: JBIDE-20849
URL: https://issues.jboss.org/browse/JBIDE-20849
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.0.CR2
Reporter: Marián Labuda
Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png
There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks.
!openshift2_connection_dialog.png!
!openshift3_connection_dialog.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20848) Release publish scripts and use them
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-20848:
--------------------------------------
Summary: Release publish scripts and use them
Key: JBIDE-20848
URL: https://issues.jboss.org/browse/JBIDE-20848
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Affects Versions: 4.3.0.CR1
Reporter: Mickael Istria
Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot.
--
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 commented on JBIDE-20760:
------------------------------------
{quote}
(2015-10-01 09:33:02) ldimaggi_: nickboldt, so - we will have the unused and disabled update site, yes?
(2015-10-01 09:40:31) nickboldt: ldimaggi_: as documented in the JIRA, putting the feature BACK into the site means when a user installs the eclipse docker tooling feature, they get added to their list of available update sites in Eclipse (not JBDS) a new, *disabled* URL for the docker update site
(2015-10-01 09:40:42) nickboldt: ldimaggi_: you already agreed to this in the jira
(2015-10-01 09:40:58) ldimaggi_: nickboldt, +1 just checking
{quote}
Also +1'd by Alexey on the PR, so applied in 4.3.x and building:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=123
> 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-18820) define how to handle ide.properties and avoid parent pom to always change
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18820:
-------------------------------
Labels: devdoc (was: )
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, devdoc
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Labels: devdoc
> Fix For: 4.3.0.Final
>
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence 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:
------------------------------------
Slip to 4.3.x / 4.4.0.Alpha1.
> 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)
[ https://issues.jboss.org/browse/JBIDE-20847?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20847:
----------------------------------
Priority: Major (was: Minor)
> 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
> Labels: connection_wizard
>
> 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-20847) Only "retrieve" and "sign up here" link inside styled text should be accessible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20847?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20847:
----------------------------------
Labels: connection_wizard (was: )
> 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
> Labels: connection_wizard
>
> 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-18820) define how to handle ide.properties and avoid parent pom to always change
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18820:
-------------------------------
Component/s: devdoc
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, devdoc
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.0.Final
>
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months