[JBoss JIRA] (JBDS-2461) Wrong version number in loading screen
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBDS-2461:
---------------------------------------
Summary: Wrong version number in loading screen
Key: JBDS-2461
URL: https://issues.jboss.org/browse/JBDS-2461
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build
Affects Versions: 7.0.0.Alpha1
Reporter: Jaroslav Jankovič
Assignee: Nick Boldt
Fix For: 7.0.0.Alpha2
JBDS version number in right upper corner of Loading screen is pointing out that version of current build is 6 not 7 as it should be
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13519) Eclipse OpenShift plugin - Double quotes appear in express.conf for libra_server parameter
by Sergio Torassa (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13519?page=com.atlassian.jira.plugi... ]
Sergio Torassa updated JBIDE-13519:
-----------------------------------
Priority: Minor (was: Major)
> Eclipse OpenShift plugin - Double quotes appear in express.conf for libra_server parameter
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-13519
> URL: https://issues.jboss.org/browse/JBIDE-13519
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Fedora 17
> Eclipse Java EE IDE for Web Developers.
> Version: Juno Service Release 1
> Build id: 20121004-1855
> OpenShift Eclipse plugin: latest available
> Reporter: Sergio Torassa
> Assignee: Andre Dietisheim
> Priority: Minor
>
> When trying to create a new OpenShift project from Eclipse, the plugin cannot check the user credential, due to a typo in the express.conf file: the libra_server parameter has a double quoted value, instead of a correct single quote one. Replacing the wrong value with the correct one, the authentication is successfully completed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13519) Eclipse OpenShift plugin - Double quotes appear in express.conf for libra_server parameter
by Sergio Torassa (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13519?page=com.atlassian.jira.plugi... ]
Sergio Torassa updated JBIDE-13519:
-----------------------------------
Priority: Major (was: Minor)
> Eclipse OpenShift plugin - Double quotes appear in express.conf for libra_server parameter
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-13519
> URL: https://issues.jboss.org/browse/JBIDE-13519
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: Fedora 17
> Eclipse Java EE IDE for Web Developers.
> Version: Juno Service Release 1
> Build id: 20121004-1855
> OpenShift Eclipse plugin: latest available
> Reporter: Sergio Torassa
> Assignee: Andre Dietisheim
>
> When trying to create a new OpenShift project from Eclipse, the plugin cannot check the user credential, due to a typo in the express.conf file: the libra_server parameter has a double quoted value, instead of a correct single quote one. Replacing the wrong value with the correct one, the authentication is successfully completed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13521) SSH Key Management timeout
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-13521:
--------------------------------------
Summary: SSH Key Management timeout
Key: JBIDE-13521
URL: https://issues.jboss.org/browse/JBIDE-13521
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.1.0.Alpha1
I was able to create connection to openshift.redhat.com with one of my account (username 'sbunciak' - RHN account, so username without the email ending '@redhat.com')
When trying to remove key i get:
An internal error occurred during: "Removing SSH key id1111...".
{code}
com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/user/keys/id1111, connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:111)
at com.openshift.internal.client.RestService.request(RestService.java:91)
at com.openshift.internal.client.RestService.request(RestService.java:76)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
at com.openshift.internal.client.SSHKeyResource$DeleteKeyRequest.execute(SSHKeyResource.java:116)
at com.openshift.internal.client.SSHKeyResource$DeleteKeyRequest.access$300(SSHKeyResource.java:109)
at com.openshift.internal.client.SSHKeyResource.destroy(SSHKeyResource.java:72)
at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.ManageSSHKeysWizardPageModel.removeKey(ManageSSHKeysWizardPageModel.java:54)
at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.ManageSSHKeysWizardPage$RemoveKeyJob.run(ManageSSHKeysWizardPage.java:292)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}
When trying to add a new key i get:
Could not add SSH key id to OpenShift
{code}
com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/user/keys, connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:111)
at com.openshift.internal.client.RestService.request(RestService.java:91)
at com.openshift.internal.client.RestService.request(RestService.java:76)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
at com.openshift.internal.client.UserResource$AddSShKeyRequest.execute(UserResource.java:266)
at com.openshift.internal.client.UserResource.putSSHKey(UserResource.java:234)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.putSSHKey(Connection.java:400)
at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.NewSSHKeyWizardPageModel.addSSHKey(NewSSHKeyWizardPageModel.java:108)
at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.AddSSHKeyJob.run(AddSSHKeyJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}
At the moment I'm not aware of any workaround - i can't use git clone,port forwarding, etc (everything that needs ssh connection)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13521) SSH Key Management timeout
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13521?page=com.atlassian.jira.plugi... ]
Stefan Bunciak commented on JBIDE-13521:
----------------------------------------
I was not able to reproduce using my other openshift accounts, only with this one.
> SSH Key Management timeout
> --------------------------
>
> Key: JBIDE-13521
> URL: https://issues.jboss.org/browse/JBIDE-13521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Alpha1
>
>
> I was able to create connection to openshift.redhat.com with one of my account (username 'sbunciak' - RHN account, so username without the email ending '@redhat.com')
> When trying to remove key i get:
> An internal error occurred during: "Removing SSH key id1111...".
> {code}
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/user/keys/id1111, connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:111)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.SSHKeyResource$DeleteKeyRequest.execute(SSHKeyResource.java:116)
> at com.openshift.internal.client.SSHKeyResource$DeleteKeyRequest.access$300(SSHKeyResource.java:109)
> at com.openshift.internal.client.SSHKeyResource.destroy(SSHKeyResource.java:72)
> at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.ManageSSHKeysWizardPageModel.removeKey(ManageSSHKeysWizardPageModel.java:54)
> at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.ManageSSHKeysWizardPage$RemoveKeyJob.run(ManageSSHKeysWizardPage.java:292)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> When trying to add a new key i get:
> Could not add SSH key id to OpenShift
> {code}
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/user/keys, connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:111)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.UserResource$AddSShKeyRequest.execute(UserResource.java:266)
> at com.openshift.internal.client.UserResource.putSSHKey(UserResource.java:234)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.putSSHKey(Connection.java:400)
> at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.NewSSHKeyWizardPageModel.addSSHKey(NewSSHKeyWizardPageModel.java:108)
> at org.jboss.tools.openshift.express.internal.ui.wizard.ssh.AddSSHKeyJob.run(AddSSHKeyJob.java:35)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> At the moment I'm not aware of any workaround - i can't use git clone,port forwarding, etc (everything that needs ssh connection)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13519) Eclipse OpenShift plugin - Double quotes appear in express.conf for libra_server parameter
by Sergio Torassa (JIRA)
Sergio Torassa created JBIDE-13519:
--------------------------------------
Summary: Eclipse OpenShift plugin - Double quotes appear in express.conf for libra_server parameter
Key: JBIDE-13519
URL: https://issues.jboss.org/browse/JBIDE-13519
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Environment: Fedora 17
Eclipse Java EE IDE for Web Developers.
Version: Juno Service Release 1
Build id: 20121004-1855
OpenShift Eclipse plugin: latest available
Reporter: Sergio Torassa
Assignee: Andre Dietisheim
When trying to create a new OpenShift project from Eclipse, the plugin cannot check the user credential, due to a typo in the express.conf file: the libra_server parameter has a double quoted value, instead of a correct single quote one. Replacing the wrong value with the correct one, the authentication is successfully completed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13335:
-----------------------------------
Fix Version/s: 4.1.0.Final
Adding Fix version for JBT 4.1.0 and JBDS 7.0.0, this should be fixed also in these versions.
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.1.Final, 4.1.0.Final
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13407:
-----------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.0.Alpha1)
> Jar signing for JBT plugins/features
> ------------------------------------
>
> Key: JBIDE-13407
> URL: https://issues.jboss.org/browse/JBIDE-13407
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, updatesite
> Affects Versions: 3.3.2, 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png
>
>
> Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product.
> Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months