[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ]
Paul Leacu edited comment on JBDS-3384 at 6/4/15 8:49 AM:
----------------------------------------------------------
I talked to Nick - they're expecting to have their Mars Beta1 repos ready by Monday. I'll pick up from there and from mars/201505291000-RC2/ for a new JBTIS TP (4.3.0.Beta1).
btw - these are the terminal-related IUs that I'll pick up from RC2:
{code}
<!-- JBIDE-17686 Required by rse.terminals, but not in the new RSE 4.0 M7 site -->
<unit id="org.eclipse.rse.services" version="3.3.0.201403100950"/>
<unit id="org.eclipse.rse.services.ssh" version="3.2.100.201403281521"/>
<unit id="org.eclipse.rse.core" version="3.3.100.201407181907"/>
<unit id="org.eclipse.rse.ui" version="3.3.100.201503112018"/>
<unit id="org.eclipse.rse.connectorservice.ssh" version="2.1.300.201505220524"/>
<unit id="org.eclipse.tm.terminal.control.feature.feature.group" version="4.0.0.201505230816"/>
<unit id="org.eclipse.core.expressions" version="3.5.0.v20150421-2214"/>
<unit id="org.eclipse.tm.terminal.view.core" version="4.0.0.201505101440"/>
<unit id="org.eclipse.tm.terminal.view.ui" version="4.0.0.201505081521"/>
<unit id="org.eclipse.tm.terminal.view.ui.rse" version="4.0.0.201505101444"/>
<unit id="org.eclipse.tm.terminal.connector.serial.feature.feature.group" version="4.0.0.201505230816"/>
<unit id="org.eclipse.tm.terminal.connector.ssh.feature.feature.group" version="4.0.0.201505230816"/>
<unit id="org.eclipse.tm.terminal.connector.telnet.feature.feature.group" version="4.0.0.201505230816"/>
<unit id="org.eclipse.tm.terminal.connector.local.feature.feature.group" version="4.0.0.201505230816"/>
{code}
was (Author: pleacu):
I talked to Nick - they're expecting to have their Mars Beta1 repos ready by Monday. I'll pick up from there and from mars/201505291000-RC2/ for a new JBTIS TP (4.3.0.Beta1).
> Investigate how the terminal changes in Mars will/should affect us
> -------------------------------------------------------------------
>
> Key: JBDS-3384
> URL: https://issues.jboss.org/browse/JBDS-3384
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, forge, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 9.0.0.Beta2
>
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBDS-3384:
----------------------------------
I talked to Nick - they're expecting to have their Mars Beta1 repos ready by Monday. I'll pick up from there and from mars/201505291000-RC2/ for a new JBTIS TP (4.3.0.Beta1).
> Investigate how the terminal changes in Mars will/should affect us
> -------------------------------------------------------------------
>
> Key: JBDS-3384
> URL: https://issues.jboss.org/browse/JBDS-3384
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, forge, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 9.0.0.Beta2
>
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19108) Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19108?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19108.
---------------------------------
Closing.
> Choosing OpenShift Server adapter and then another server in create server wizard list causes impossibility to run server
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19108
> URL: https://issues.jboss.org/browse/JBIDE-19108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
> Attachments: JBIDE-19108_1.png, JBIDE-19108_2.png, JBIDE-19108_3.png, server_already_running.png
>
>
> If I am creating new server in Servers view via New Server wizard and I select in tree at first OpenShift Server Adapter and then e.g. Wildfly 8.x server, then created server cannot be started. There is a warning there there is server running on openshift.redhat.com:8080. User has to delete such server from servers view and create a new one without selecting OpenShift Server Adapter in server type selection.
> !server_already_running.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-15884:
--------------------------------
Labels: new_and_noteworthy (was: )
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Ilya Buziuk closed JBIDE-15884.
-------------------------------
Resolution: Done
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months