[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-24382:
---------------------------------------
Hi [~nickboldt], [~odockal], I have retested docker tooling in 10.4.0.GA, Build id: GA-v20170504-2114-B29, with docker tooling 2.3.0.201404251823 and I have not found any issues with this version.
[~rhopp] can you please retest it with OpenShift? Thanks :)
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Ondrej Dockal
> Fix For: 4.4.4.Final
>
> Attachments: BYOE_keep.png, BYOE_show.png, BYOE_update.png, byoe_afeter_install.png, byoe_keep2.png, byoe_update2.png, devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt, p2diff_460.txt, p2diff_460_summary.txt, processing_information_1.png, processing_information_2.png, processing_information_3.png, rh_central_remediation_page_keep.png, rh_central_remediation_page_show.png
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4195) Remove Software/Update page when installed from RPM.
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4195?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4195:
------------------------------------
Commits have been reverted successfully. Are there any other things to do? Could we close this jira?
> Remove Software/Update page when installed from RPM.
> ----------------------------------------------------
>
> Key: JBDS-4195
> URL: https://issues.jboss.org/browse/JBDS-4195
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: central, central-update
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA, 10.4.0.GA, 11.0.0.AM1
>
> Attachments: jbds4195.usage.properties.png, jbds4195.usage.properties.txt
>
>
> In order to avoid presenting JBDS-4175 to users, a workaround is to not show the Software/Updates tab when installation comes from RPM. We'll use the same sort of identification as in JBDS-4014, a suffix of "|Devstudio" indicating that the install is from RPM, eg., this screengrab from Google Analytics:
> http://imgur.com/kyspoAn
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.com as default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24383:
------------------------------------------
[~jeffmaury] I dont, the text is always shown, there's no way to know if the user has an account. That's how it always was for OpenShift 2 before it became unsuggested to attract new users to v2 but to wait for the v3 online option.
To me it is far more helpful for a new user to point him how to sign up rather than to show him documentation which is only helpful once you have a server.
> Connection wizard: offer openshift.com as default server
> --------------------------------------------------------
>
> Key: JBIDE-24383
> URL: https://issues.jboss.org/browse/JBIDE-24383
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
> Attachments: connection-wizard-signup-link.png
>
>
> now that https://openshift.com is launched we should provide it as default server in the connection wizard.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months