[JBoss JIRA] (JBIDE-19829) Connection wizard: Add Oauth support
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19829:
-------------------------------------
Summary: Connection wizard: Add Oauth support (was: Add Oauth support to the Openshift Connection Wizard)
> Connection wizard: Add Oauth support
> ------------------------------------
>
> Key: JBIDE-19829
> URL: https://issues.jboss.org/browse/JBIDE-19829
> 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, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.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, 10 months
[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19829:
------------------------------------------
resolving this for now since we merged the code in and will file remaining issue to new jiras.
> Add Oauth support to the Openshift Connection Wizard
> ----------------------------------------------------
>
> Key: JBIDE-19829
> URL: https://issues.jboss.org/browse/JBIDE-19829
> 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, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.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, 10 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19795:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/488, https://github.com/jbosstools/jbosstools-jst/pull/489 (was: https://github.com/jbosstools/jbosstools-jst/pull/488)
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: javascript
> Affects Versions: 4.3.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Final
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> Bower tooling should initially support several bower API commands :
> |Command||Description|
> | *bower init* |creates a *bower.json* file|
> |*bower install <package>*|installs packages to *bower_components* folder|
> |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory|
> |*bower update* |updates installed packages to their newest version according to *bower.json*|
> Basically, the main idea of the implementation is the following:
> Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *The main questions & proposals:*
> 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
> 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
> 3. Implementation details:
> - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* )
> - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19829:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
> Add Oauth support to the Openshift Connection Wizard
> ----------------------------------------------------
>
> Key: JBIDE-19829
> URL: https://issues.jboss.org/browse/JBIDE-19829
> 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, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.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, 10 months