<div dir="ltr">You can find in maven under:<div><br></div><div>org.jboss.aesh:aesh:0.46-SNAPSHOT</div><div><br></div><div>The github repo/org is here: <a href="https://github.com/aeshell/aesh">https://github.com/aeshell/aesh</a></div>
<div><br></div><div>~Lincoln</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jan 11, 2014 at 3:58 PM, Ståle W Pedersen <span dir="ltr"><<a href="mailto:spederse@redhat.com" target="_blank">spederse@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi, ivan it is most likely an æsh bug (which forge uses for shell<br>
interaction). to quickly debug æsh you could just start a simple example<br>
program like: java -cp aesh-0.46-SNAPSHOT.jar AeshExample<br>
- you should have the aesh jar in your local mvn cache.<br>
<br>
AeshExample should log to TMP/aesh.log and there is a log line starting<br>
with "GOT:" for each input. that input should match whatever is<br>
specified in Key.java (in æsh).<br>
from what you've described above it seems that ive introduced a bug in a<br>
later release with this or it might also be the parsing. whatever you<br>
find out will no matter help.<br>
<br>
regards, ståle<br>
<div><div class="h5"><br>
On 11.01.14 21:18, Ivan St. Ivanov wrote:<br>
>Hi folks,<br>
><br>
>I just created this JIRA: <a href="https://issues.jboss.org/browse/FORGE-1425" target="_blank">https://issues.jboss.org/browse/FORGE-1425</a><br>
><br>
>As I wrote in the first email, I would like to help resolving it. I just<br>
>need some guidance on where to look. George asked me to run the unit tests<br>
>and I tried. However, the addon-manager tests failed and I couldn't find<br>
>the reason. :(<br>
><br>
>Cheers,<br>
>Ivan<br>
><br>
><br>
>On Sat, Jan 11, 2014 at 7:54 PM, Lincoln Baxter, III <<br>
><a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@gmail.com</a>> wrote:<br>
><br>
>> Yes, thank you for finding these issues! Looks like we know what we will<br>
>> be working on next few days :)<br>
>><br>
>><br>
>> On Sat, Jan 11, 2014 at 12:40 PM, George Gastaldi <<a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a>>wrote:<br>
>><br>
>>> Ivan,<br>
>>><br>
>>> Could you open a JIRA with these issues and mark it as Blocker? We can't<br>
>>> release 2.0.0.Final unless this is fixed.<br>
>>><br>
>>> Em 08/01/2014, às 11:18, "Ivan St. Ivanov" <<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>><br>
>>> escreveu:<br>
>>><br>
>>> Sorry, forgot to mention that this is with snapshot from December, 29th.<br>
>>> The situation was the same with all the previous betas and alphas.<br>
>>><br>
>>><br>
>>> On Wed, Jan 8, 2014 at 3:13 PM, George Gastaldi <<a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a>>wrote:<br>
>>><br>
>>>> Thanks for the feedback ivan.<br>
>>>> Are you testing against the latest snapshot?<br>
>>>><br>
>>>> Best Regards,<br>
>>>> George<br>
>>>><br>
>>>> Em 08/01/2014, às 11:10, "Ivan St. Ivanov" <<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>><br>
>>>> escreveu:<br>
>>>><br>
>>>> Hi folks,<br>
>>>><br>
>>>> As I promised, here is a [intended-to-be] short feedback about the new<br>
>>>> Forge 2 shell. As some of you know, I use Windows (Really? OK...). So I<br>
>>>> will be very happy to help you solve the issues besides merely reporting<br>
>>>> them:<br>
>>>><br>
>>>> * The history doesn't work. That is, when you press up and down arrows<br>
>>>> instead of the previous commands, you get this: αH<br>
>>>><br>
>>>> * Backspace doesn't work. When I press it, the cursor just comes back to<br>
>>>> the previous position without deleting the character there. If I just write<br>
>>>> something there, the old symbol is overwritten by the new one, but at the<br>
>>>> end after pressing enter it looks like you never entered anything after<br>
>>>> pressing backspace. For example:<br>
</div></div>>>>> 1) I write *new-project --namek*<br>
<div class="im">>>>> 2) I notice the typo and press backspace<br>
>>>> 3) k doesn't get deleted, but I overwrite it with d<br>
</div>>>>> 4) Then I complete my command to look like this: *new-project --named<br>
>>>> test*<br>
>>>> 5) Forge's output is: *Project name must be specified.*<br>
<div class="im">>>>><br>
>>>> * As you know on windows the full path to a file or directory is<br>
>>>> <drive-letter>:\<dir1>\<dir2><br>
</div>>>>> 1) If I try to do *cd c:\temp\forge*, Forge blows with exception:<br>
<div class="im">>>>> org.jboss.forge.addon.resource.ResourceException: [FileResourceImpl] can<br>
>>>> have no<br>
>>>> children<br>
>>>> at<br>
>>>> org.jboss.forge.addon.resource.AbstractFileResource.getChild(Abstract<br>
>>>> FileResource.java:78)<br>
>>>> at<br>
>>>> org.jboss.forge.addon.shell.util.PathspecParser.resolve(PathspecParse<br>
>>>> r.java:232)<br>
>>>> at<br>
>>>> org.jboss.forge.addon.shell.commands.CdCommand.execute(CdCommand.java<br>
>>>> :71)<br>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
>>>> at<br>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.<br>
>>>> java:57)<br>
>>>> at<br>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces<br>
>>>> sorImpl.java:43)<br>
>>>> at java.lang.reflect.Method.invoke(Method.java:606)<br>
>>>> 2) Somehow I noticed that I may use the paths without the drive<br>
>>>> letter, e.g. just \<dir1>\<dir2>. It is legal to do it in Windows, but thus<br>
>>>> you can't change to a directory located on a different drive. For example<br>
>>>> cd \temp\forge will change to c:\temp\forge if you are currently in c:. So<br>
</div>>>>> I tried *cd \temp\forge*, but the result was the same [exception].<br>
>>>> 3) If I am in the root directory (c:\) and I run *cd temp\forge*, I<br>
>>>> don't get exception, but ****ERROR*** tempforge\: No such file or<br>
>>>> directory*. The interesting thing is that I ran that command by<br>
<div class="im">>>>> pressing tab, i.e. counting on the command completion of the shell, which<br>
>>>> obviously works fine.<br>
>>>><br>
</div>>>>> I made the cd command work by just running *cd /temp/forge* (notice<br>
<div class="HOEnZb"><div class="h5">>>>> the forward slashes)<br>
>>>><br>
>>>><br>
>>>> If you wish, I may add these observations as JIRA items, probably as<br>
>>>> children to this one: <a href="https://issues.jboss.org/browse/FORGE-1387" target="_blank">https://issues.jboss.org/browse/FORGE-1387</a>. Bear<br>
>>>> in mind that all the reported features work in Forge 1 even on Windows ;)<br>
>>>><br>
>>>> We can discuss these in today's meeting.<br>
>>>><br>
>>>> Cheers,<br>
>>>> Ivan<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> forge-dev mailing list<br>
>>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> forge-dev mailing list<br>
>>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>>>><br>
>>><br>
>>> _______________________________________________<br>
>>> forge-dev mailing list<br>
>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> forge-dev mailing list<br>
>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Lincoln Baxter, III<br>
>> <a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
>> "Simpler is better."<br>
>><br>
>> _______________________________________________<br>
>> forge-dev mailing list<br>
>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>><br>
<br>
>_______________________________________________<br>
>forge-dev mailing list<br>
><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
><a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br>
<a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."
</div>