[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
SJ Cox updated JBDS-3605:
-------------------------
Attachment: RedHatDeveloperStudio_BrandingDeliverables.zip
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: RedHatDeveloperStudio_BrandingDeliverables.zip
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
SJ Cox commented on JBDS-3605:
------------------------------
[~nickboldt] and [~maxandersen], I've attached a zip of the assets and also posted the Overview page so you can view all deliverables next to each other. Please note that the final asset for the splash screen does not have the 9 on it since that will be coded in.
Let me know if you have any questions, thanks!
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21829) Error while opening Eclipse with OpenShift Server Editor opened
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21829:
---------------------------------------
[~fbricon] there is a tracing tab when launching the ide...or you can enable it in your preferences, presumably if you were to install the plugin.
> Error while opening Eclipse with OpenShift Server Editor opened
> ---------------------------------------------------------------
>
> Key: JBIDE-21829
> URL: https://issues.jboss.org/browse/JBIDE-21829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597
> !MESSAGE An internal error occurred during: "Setting connection, deploy project...".
> !STACK 0
> com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256)
> at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This error also happens when the editor is closed at start-up and opened later on.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3683) Browsersim fails to open with OpenJDK
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3683:
----------------------------------
Summary: Browsersim fails to open with OpenJDK
Key: JBDS-3683
URL: https://issues.jboss.org/browse/JBDS-3683
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: upstream
Affects Versions: 9.1.0.CR1
Reporter: Len DiMaggio
Priority: Blocker
The error message displayed is:
"To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher."
Also see <a href="http://tools.jboss.org/documentation/faq/browsersim.html">BrowserSim FAQ</a>.
Stack trace:
org.eclipse.swt.SWTError: To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher.
at org.jboss.tools.browsersim.ui.launch.BrowserSimRunner.main(BrowserSimRunner.java:87)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21829) Error while opening Eclipse with OpenShift Server Editor opened
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21829:
-------------------------------------
how do you enable tracing?
> Error while opening Eclipse with OpenShift Server Editor opened
> ---------------------------------------------------------------
>
> Key: JBIDE-21829
> URL: https://issues.jboss.org/browse/JBIDE-21829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597
> !MESSAGE An internal error occurred during: "Setting connection, deploy project...".
> !STACK 0
> com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256)
> at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This error also happens when the editor is closed at start-up and opened later on.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month