[JBoss JIRA] (JBDS-4731) Missing datatools.enablement features since 12.0
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4731?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal commented on JBDS-4731:
-------------------------------------
[~nickboldt] I can say that it seems that all the plugins are available in devstudio, besides that, I can see the proper wizard and list of all available drivers:
!Screenshot_20190320_121334.png|thumbnail!
Verified on devstudio 12.11.0.GA-v20190313-1333-B4198.
> Missing datatools.enablement features since 12.0
> ------------------------------------------------
>
> Key: JBDS-4731
> URL: https://issues.jboss.org/browse/JBDS-4731
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.0.0.GA
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Major
> Fix For: 12.10.0.AM1
>
> Attachments: 12.9.0.GA.png, 2018-09.png, Screenshot_20190320_121334.png
>
>
> As reported on StackOverflow, it is not possible to create third parties JBDC drivers since 12.0.0.GA. Some org.eclipse.datatools.enablement features are misssing. See the captures for the list
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBDS-4731) Missing datatools.enablement features since 12.0
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4731?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal updated JBDS-4731:
--------------------------------
Attachment: Screenshot_20190320_121334.png
> Missing datatools.enablement features since 12.0
> ------------------------------------------------
>
> Key: JBDS-4731
> URL: https://issues.jboss.org/browse/JBDS-4731
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.0.0.GA
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Major
> Fix For: 12.10.0.AM1
>
> Attachments: 12.9.0.GA.png, 2018-09.png, Screenshot_20190320_121334.png
>
>
> As reported on StackOverflow, it is not possible to create third parties JBDC drivers since 12.0.0.GA. Some org.eclipse.datatools.enablement features are misssing. See the captures for the list
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-25814:
----------------------------------
Sprint: devex #164 April 2019 (was: devex #163 March 2019)
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Josef Kopriva
> Priority: Major
> Labels: server_adapter_wizard
> Fix For: 4.11.0.Final
>
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-25814:
----------------------------------
Sprint: devex #163 March 2019
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Josef Kopriva
> Priority: Major
> Labels: server_adapter_wizard
> Fix For: 4.11.0.Final
>
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months