<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Max,<br>
<br>
I verified today that the forge runtime issue is fixed in forge
runtime 1.1.2.Final.<br>
What do you think, can we get it into JBT 4.0.0.CR1? <br>
I opened a jira for it:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://issues.jboss.org/browse/JBIDE-13108">https://issues.jboss.org/browse/JBIDE-13108</a><br>
<br>
Thanks.<br>
<br>
-Pavol.<br>
<br>
<div class="moz-cite-prefix">On 11/17/2012 01:49 AM, Max Rydahl
Andersen wrote:<br>
</div>
<blockquote
cite="mid:C4798602-0200-4F13-B212-D74D4F295E9E@redhat.com"
type="cite">
<blockquote type="cite">
<pre wrap="">there is a bug in forge runtime <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/FORGEPLUGINS-41">https://issues.jboss.org/browse/FORGEPLUGINS-41</a> and because of that issue you cannot deploy from CLI/Forge console in JBT.
Can we somehow take care that it will be fixed in time before JBT 4.0.0.Final?
</pre>
</blockquote>
<pre wrap="">
Pavol - we don't control Forge runtime, just the console. I assume this bug happens outside jbosstools, on the CLI too ?
That said, the bug was commented 10th October by Lincoln asking for verification/details.
Could you please provide those so the forge runtime team can be made aware of it ?
Thanks,
/max</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Pavol Srna
QA Engineer, JBDS
Phone: +420 532 294 352
irc: psrna
Red Hat Czech
Purkynova 99, 612 00 Brno, Czech Republic</pre>
</body>
</html>