[JBoss JIRA] (JBIDE-19897) Remove check server type
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19897:
-------------------------------------
Summary: Remove check server type
Key: JBIDE-19897
URL: https://issues.jboss.org/browse/JBIDE-19897
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Fix For: 4.3.0.Beta1
Attachments: check-server-type-disabled.png, ok-enabled.png, retrieve-error.png
Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth
* Remove server type verify button
* Add v3 auth box (Auto/OAuth/Basic)
* Optional...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19897) Remove check server type
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19897:
----------------------------------
Attachment: (was: enlessly-loading.png)
> Remove check server type
> ------------------------
>
> Key: JBIDE-19897
> URL: https://issues.jboss.org/browse/JBIDE-19897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png, ok-enabled.png, retrieve-error.png
>
>
> Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth
> * Remove server type verify button
> * Add v3 auth box (Auto/OAuth/Basic)
> * Optional...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19897) Remove check server type
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19897:
----------------------------------
Attachment: (was: Proposed Connection Wizard Chages.png)
> Remove check server type
> ------------------------
>
> Key: JBIDE-19897
> URL: https://issues.jboss.org/browse/JBIDE-19897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png, ok-enabled.png, retrieve-error.png
>
>
> Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth
> * Remove server type verify button
> * Add v3 auth box (Auto/OAuth/Basic)
> * Optional...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBDS-3445) Request users to choose java 8 or higher when installing JBDS 9
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3445?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3445.
---------------------------------
Resolution: Done
released to master. For version higher than 1.8 installer shows generic warning (that part was implemented before)
> Request users to choose java 8 or higher when installing JBDS 9
> ---------------------------------------------------------------
>
> Key: JBDS-3445
> URL: https://issues.jboss.org/browse/JBDS-3445
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, installer
> Affects Versions: 9.0.0.Alpha2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta1
>
>
> Based on the decision on JBDS PM call today, we will only support JBDS to be running on Java 8 or higher in 9.0.0.Beta1. So the installer shouldn't let users choose java 7 for the installation.
> Just to be clear: The installer itself will still work fine with java 6 or 7.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
Connecting to local (or remote) jmx loads jars from the LOCAL runtime installation into a ClassLoader for the purposes of executing the remote jmx commands.
This differs from our management plugins, which bundle all deps (remoting, dmr, threads, etc) for each breaking version in the server.
The request here is to connect to a remote server for JMX while NOT having a local jboss-as / wildfly from which to pull JMX classes / jars. This would require bundling more libs (jboss-client-all.jar) for each different app server. This will balloon the size of our deps, and probably require new plugins. (We currently have a management.71 and management.80... now imagine adding new plugins for jmx for every app server version in the past, which requires jboss-client-all.jar for each breaking version).
> Cannot connect to remote server in JMX Navigator
> ------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months