[ https://issues.jboss.org/browse/JBIDE-20096?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20096:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> Application wizard: creating eap-simple from templates and show in browser tries to open 'eap.local'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20096
> URL: https://issues.jboss.org/browse/JBIDE-20096
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.x
>
>
> not sure what is to "blame" here but creating app from https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v3beta1) results in app getting created but show in browser wants me to go to "eap.local" which pretty sure that is not something that exist from the outside.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBIDE-20096?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20096:
-------------------------------------
Show in Browser properly opens the route for an app created with eap-basic.sti, on the engint platform.
If the problem occurs on local OpenShift installations, there's nothing much we can do from a tooling standpoint.
> Application wizard: creating eap-simple from templates and show in browser tries to open 'eap.local'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20096
> URL: https://issues.jboss.org/browse/JBIDE-20096
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.0.CR1
>
>
> not sure what is to "blame" here but creating app from https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v3beta1) results in app getting created but show in browser wants me to go to "eap.local" which pretty sure that is not something that exist from the outside.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBDS-3495?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3495:
----------------------------------
/me sets QA_ACK because QA opened this issue. /me shakes my head at JIRA's silly workflow because it can't see that a QE person opening a JIRA by definition means they ACK the request.
> JBDS 9.0.0.beta is preconfigured with an Eclipse Docker tooling site
> --------------------------------------------------------------------
>
> Key: JBDS-3495
> URL: https://issues.jboss.org/browse/JBDS-3495
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 9.0.0.Beta2
> Reporter: Len DiMaggio
> Assignee: Max Rydahl Andersen
> Fix For: 9.0.0.CR1
>
> Attachments: DockerTooling.png
>
>
> See attached screenshot - JBDS 9.0.0.beta2 is preconfigured with this update site:
> http://download.eclipse.org/linuxtools/updates-docker-nightly
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/JBDS-3495?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3495:
-------------------------------------------
I think this must be a bug in the docker updatesite - seems very weird it needs to add the nightly updatesite that it is already coming from.
> JBDS 9.0.0.beta is preconfigured with an Eclipse Docker tooling site
> --------------------------------------------------------------------
>
> Key: JBDS-3495
> URL: https://issues.jboss.org/browse/JBDS-3495
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 9.0.0.Beta2
> Reporter: Len DiMaggio
> Assignee: Max Rydahl Andersen
> Fix For: 9.0.0.CR1
>
> Attachments: DockerTooling.png
>
>
> See attached screenshot - JBDS 9.0.0.beta2 is preconfigured with this update site:
> http://download.eclipse.org/linuxtools/updates-docker-nightly
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)