[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19548:
------------------------------------------
the update site now contains updated binaries that i tested and work, the auth-form showed up for OpenShift v3 and I could create a connection.
> Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19548
> URL: https://issues.jboss.org/browse/JBIDE-19548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: 3.0.0.Alpha2-v20150401-1037-B749
> Reporter: Ma Deshuai
> Assignee: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha2
>
> Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png
>
>
> 1. Open connection wizard
> 2. Select the server type to OpenShift 3
> 3. Input the server url
> 4. Click the finish button to connect the v3 server
> Result:
> 2. In the authentication, there is no place to input the username and password.
> 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19551) Ionic Palette: Empty list item
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19551?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19551:
-----------------------------------
Description:
In New List wizard, if there is more than one item then all items but the first are empty:
!list.png!
> Ionic Palette: Empty list item
> ------------------------------
>
> Key: JBIDE-19551
> URL: https://issues.jboss.org/browse/JBIDE-19551
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
> Attachments: list.png
>
>
> In New List wizard, if there is more than one item then all items but the first are empty:
> !list.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19551) Ionic Palette: Empty list item
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-19551:
--------------------------------------
Summary: Ionic Palette: Empty list item
Key: JBIDE-19551
URL: https://issues.jboss.org/browse/JBIDE-19551
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha2
Attachments: list.png
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19548:
------------------------------------------
I corrected our build settings and added a warning to the Eclipse logs (<workspace-folder>/.metadata/.log) when no form is found for a given selected server type.
merged the fix and pushed it to upstream/master.
I tried the result locally and it worked for me. Now waiting for the build to finish on jenkins so that the update site gets the updated artifacts.
> Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19548
> URL: https://issues.jboss.org/browse/JBIDE-19548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: 3.0.0.Alpha2-v20150401-1037-B749
> Reporter: Ma Deshuai
> Assignee: Andre Dietisheim
> Labels: connection_wizard
> Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png
>
>
> 1. Open connection wizard
> 2. Select the server type to OpenShift 3
> 3. Input the server url
> 4. Click the finish button to connect the v3 server
> Result:
> 2. In the authentication, there is no place to input the username and password.
> 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3394:
------------------------------------
Just to make this very clear:
* We are not dropping the support for building/running engines older than 3.5.0
* If a user wants to download a cordova platform using JBDS/JBT, for either a new or existing/legacy project, only versions 3.5.0 and later will be available
Correct?
> Use cordova platform downloads from npm
> ---------------------------------------
>
> Key: JBDS-3394
> URL: https://issues.jboss.org/browse/JBDS-3394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.Alpha2
>
>
> Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available.
> Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm.
> cordova-ios
> ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ]
> cordova-android
> [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ]
> cordova-wp8
> [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ]
Karel Piwko commented on JBDS-3394:
-----------------------------------
Looks good to me from pov of mobile qe.
> Use cordova platform downloads from npm
> ---------------------------------------
>
> Key: JBDS-3394
> URL: https://issues.jboss.org/browse/JBDS-3394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.Alpha2
>
>
> Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available.
> Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm.
> cordova-ios
> ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ]
> cordova-android
> [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ]
> cordova-wp8
> [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years