[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-16355.
------------------------------------
Resolution: Done
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta1
>
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16634) No output to console using rse mode
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16634?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-16634:
-------------------------------------
{code}
IServer s = ServerCore.findServer(serverId);
IShellService service = findShellService(s);
try {
- IHostShell hs = service.runCommand(initialWorkingDirectory,
- command, environment, monitor);
+ IHostShell hs = service.launchShell(initialWorkingDirectory, environment, new NullProgressMonitor());
listener = new IHostShellOutputListener() {
public void shellOutputChanged(IHostShellChangeEvent event) {
IHostOutput[] lines = event.getLines();
@@ -104,6 +104,7 @@ public class RSEHostShellModel {
};
startupShell = hs;
startupShell.addOutputListener(listener);
+ hs.writeToShell(command);
return hs;
{code}
> No output to console using rse mode
> -----------------------------------
>
> Key: JBIDE-16634
> URL: https://issues.jboss.org/browse/JBIDE-16634
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta1
>
>
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16634) No output to console using rse mode
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16634?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-16634:
-------------------------------------
The bug seems caused by the following:
1) the initial command sent to the server ends with a &
2) our tools then sends an echo JBTOOLS_SERVER_START_CMD:\"$! which shows the process id of the most recent command (so we know the pid)
During 1), we use the wrong API. Instead of creating a shell, and then sending the 2 commands, we instead call IShellService-object.launchCommand(etc), and then try to launch a second command on the same shell. The effect this has is that once the first command is completed, the host shell shuts down (though the server still runs). The presence of the & causes the remote command to complete immediately. This also means we don't get to know the host shell id.
Somehow this is either a regression or a bugfix in rse. From all the reading, though, it seems its a bug fix in rse and that we were using the incorrect API which just happened to work.
> No output to console using rse mode
> -----------------------------------
>
> Key: JBIDE-16634
> URL: https://issues.jboss.org/browse/JBIDE-16634
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta1
>
>
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16634) No output to console using rse mode
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16634?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-16634:
-------------------------------------
When launching a server (say eap6.1) using rse (and local host), the console shows no output. Debug output shows the following:
!ENTRY org.eclipse.rse.services.local 4 0 2014-02-21 14:58:12.789
!MESSAGE Unexpected exception
!STACK 0
java.io.IOException: Stream closed
at java.io.BufferedReader.ensureOpen(BufferedReader.java:115)
at java.io.BufferedReader.ready(BufferedReader.java:437)
at org.eclipse.rse.internal.services.local.shells.LocalShellOutputReader.internalReadLine(LocalShellOutputReader.java:205)
at org.eclipse.rse.services.shells.AbstractHostShellOutputReader.handle(AbstractHostShellOutputReader.java:74)
at org.eclipse.rse.services.shells.AbstractHostShellOutputReader.run(AbstractHostShellOutputReader.java:180)
> No output to console using rse mode
> -----------------------------------
>
> Key: JBIDE-16634
> URL: https://issues.jboss.org/browse/JBIDE-16634
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta1
>
>
--
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
12 years, 2 months