[JBoss JIRA] (ERT-249) Add Registry Account UI improvement [EBZ#495693]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-249:
---------------------------------------
Summary: Add Registry Account UI improvement [EBZ#495693]
Key: ERT-249
URL: https://issues.jboss.org/browse/ERT-249
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
I suggest to add note/change labels in dialog Preferences->Docker->Registry Accounts-> Add .
In Server Address could be just username on Docker Hub or address of the OpenShift Docker Registry - this should be mentioned at least as a note or as a tooltip.
This dialog could be also wider(if server address longer...).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-729) Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-729?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-729:
-------------------------------------------
[~pleacu] just to clarify what I referred to in our chat since you seem to have mixed up the two concerns :)
A) the old compatiblity plugin has some code/sideeffects that (can) add to startup time thus should be avoided.
That is independent of Birt.
B) Birt itself is no longer very active and the parts we did in core (jbosstools-birt) never made it to a product so we don't maintain it anymore and removed it. I think Teiid designer only are using Birt for its mongodb datasources but i'm not sure - but if it is teiid should probably make sure to get involved upstream to either help maintain that part or help on moving it out of Birt if we really don't need anything else from Birt.
> Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
> ---------------------------------------------------------------------------
>
> Key: JBTIS-729
> URL: https://issues.jboss.org/browse/JBTIS-729
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform, teiid
> Affects Versions: 4.4.0.Alpha1-TP, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Barry LaFond
> Fix For: 4.4.0.Alpha1-TP
>
>
> org.eclipse.core.runtime.compatibility was removed from the JBT and devstudio target platforms because nothing in JBT/devstudio requires it any more.
> As a result, when you try to install Teiid Designer into the staged JBT 4.4.0.Final or devstudio 10.0.0.GA via Central, you get this error:
> {code}
> !MESSAGE Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.eclipse.core.runtime.compatibility [3.2.200,4.0.0)' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3865:
--------------------------------
Sprint: (was: devex #115 May 2016)
> Platform installer should warn about known bad versions of Vagrant.
> -------------------------------------------------------------------
>
> Key: JBDS-3865
> URL: https://issues.jboss.org/browse/JBDS-3865
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Vagrant 1.8.1 installed
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.GA
>
>
> The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list.
> Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months