<div dir="ltr">Hi Stale,<div><br></div><div>I was using the version coming from the maven repository. But tonight I will pull your latest changes, will build aesh and then will build Forge. Hopefully it will work now :)</div>
<div><br></div><div>Thanks for your effort!</div><div>Ivan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 20, 2014 at 2:03 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, thanks for the feedback. there was a bug in one of the tests that<br>
caused the latest version of æsh not being deployed on friday. so unless<br>
you built æsh from source it would probably fail on saturday as well :/<br>
<br>
- im hoping its fixed now, if not im at a loss on what's wrong since the<br>
output should be "correct" ansi.<br>
<span class="HOEnZb"><font color="#888888"><br>
ståle<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 18.01.14 22:08, Ivan St. Ivanov wrote:<br>
>... ah, forgot it, here is the ANSI string:<br>
><br>
> [;39;49m[ [;34mforge [;39m]$<br>
><br>
><br>
>On Sat, Jan 18, 2014 at 10:07 PM, Ivan St. Ivanov<br>
><<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>>wrote:<br>
><br>
>> Hi Stale,<br>
>><br>
>> After applying the latest changes, when I start Forge, after the first<br>
>> blue characters, all the characters are blue. Even after exit Forge,<br>
>> shell's foreground keeps to be blue. Here's again my code:<br>
>><br>
>> List<TerminalCharacter> prompt = new LinkedList<>();<br>
>> prompt.add(new TerminalCharacter('['));<br>
>> for (char c : currentResource.getName().toCharArray())<br>
>> {<br>
>> prompt.add(new TerminalCharacter(c, new<br>
>> TerminalColor(Color.BLUE, Color.DEFAULT)));<br>
>> }<br>
>> prompt.add(new TerminalCharacter(']', new<br>
>> TerminalColor(Color.DEFAULT, Color.DEFAULT)));<br>
>> prompt.add(new TerminalCharacter('$'));<br>
>> prompt.add(new TerminalCharacter(' '));<br>
>> return new Prompt(prompt);<br>
>><br>
>> Cheers,<br>
>> Ivan<br>
>><br>
>><br>
>> On Fri, Jan 17, 2014 at 10:46 AM, Ståle W Pedersen <<a href="mailto:spederse@redhat.com">spederse@redhat.com</a>>wrote:<br>
>><br>
>>> yes, thats the page i often refer to as well. - and its how<br>
>>> TerminalCharacters work in æsh.<br>
>>><br>
>>> ståle<br>
>>><br>
>>> On 17.01.14 8:48, Koen Aers wrote:<br>
>>> >As per this page <a href="http://en.wikipedia.org/wiki/ANSI_escape_code" target="_blank">http://en.wikipedia.org/wiki/ANSI_escape_code</a> (it's<br>
>>> wikipedia, so I don't know how correct/wrong it is) the SGR command<br>
>>> modifies the graphics rendering by adding to the previous state. So if the<br>
>>> background is blue and the foreground is red and characters are bold,<br>
>>> modifying the background to white will keep the boldness and the red<br>
>>> foreground. This also means the order of the commands should not play a<br>
>>> role.<br>
>>> ><br>
>>> >Op 17-jan.-2014, om 01:00 heeft Ståle W Pedersen het volgende geschreven:<br>
>>> ><br>
>>> >> hi, thanks for the feedback.<br>
>>> >> i see that there is indeed a bug in how TerminalCharacter is displayed.<br>
>>> >> - there is a TerminalCharacter.toString(TerminalCharacter tc) that<br>
>>> tries<br>
>>> >> to compare with the previous to reduce the data written to stream,<br>
>>> but<br>
>>> >> it has a bug and do not display it correctly.<br>
>>> >><br>
>>> >> By design it was planned that TerminalCharacter should not "reset" so<br>
>>> if<br>
>>> >> you set a TerminalCharacter with color green that color should be for<br>
>>> >> all upcoming characters unless a new one is set.<br>
>>> >><br>
>>> >> TerminalString however do in fact reset at its end (by design).<br>
>>> >><br>
>>> >> I do not know if the ordering matter, afaik it shouldnt, but it might<br>
>>> be<br>
>>> >> that that is why jansi has bleeding of colors on windows??<br>
>>> >><br>
>>> >> ståle<br>
>>> >><br>
>>> >> On 16.01.14 23:52, Ivan St. Ivanov wrote:<br>
>>> >>> Hey George, Stale,<br>
>>> >>><br>
>>> >>> I did some debugging in Forge, Aesh and even Jansi sources. Before<br>
>>> that, I<br>
>>> >>> tried to change the color of the current folder name when creating the<br>
>>> >>> prompt:<br>
>>> >>><br>
>>> >>> // in org.jboss.forge.addon.shell.ShellImpl::createPrompt()<br>
>>> >>><br>
>>> >>> for (char c : currentResource.getName().toCharArray())<br>
>>> >>> {<br>
>>> >>> prompt.add(new TerminalCharacter(c, new<br>
>>> >>> TerminalColor(Color.GREEN, Color.DEFAULT)));<br>
>>> >>> }<br>
>>> >>><br>
>>> >>> So I expect that as a result of that, all of the characters of the<br>
>>> current<br>
>>> >>> directory name would be green. However it is only the first character.<br>
>>> >>> After some more debugging, I found that for a directory called<br>
>>> *forge* the<br>
>>> >>> ANSI string passed to the Jansi library<br>
>>> >>> is: [;39;49m[ [;32mf [mo [mr [mg [me [;39m] [m$ [m (there is an ESC<br>
>>> symbol<br>
>>> >>> character before each [). As far as I got it, those constants 39, 32,<br>
>>> etc.<br>
>>> >>> denote the foreground (i.e. character) color. So, the question now is:<br>
>>> >>><br>
>>> >>> Do you have to set the foreground color once and then it is valid for<br>
>>> all<br>
>>> >>> the next characters before you set it again, or you have to set it for<br>
>>> >>> every character in the ANSI string. I think that Aesh's logic follows<br>
>>> the<br>
>>> >>> first approach, so is this correct? I'm afraid<br>
>>> >>> Jansi's AnsiOutputStream.write(int) method is a too complex FSM for<br>
>>> me in<br>
>>> >>> this late hour, so I stopped there :)<br>
>>> >>><br>
>>> >>> What else bothers me is the ordering of the style and color constants<br>
>>> for<br>
>>> >>> the first character of the prompt. Shouldn't it be the other way round<br>
>>> >>> (first the style and then the color)?<br>
>>> >>><br>
>>> >>> Cheers,<br>
>>> >>> Ivan<br>
>>> >>><br>
>>> >>><br>
>>> >>> On Wed, Jan 15, 2014 at 10:35 PM, George Gastaldi <<br>
>>> <a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a>>wrote:<br>
>>> >>><br>
>>> >>>> That's right. We expect a PR from you asap :)<br>
>>> >>>><br>
>>> >>>> Em 15/01/2014, às 18:28, "Ivan St. Ivanov" <<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a><br>
>>> ><br>
>>> >>>> escreveu:<br>
>>> >>>><br>
>>> >>>> Ah, so the coloring is in Forge, not in Aesh? Good, at least I will<br>
>>> try to<br>
>>> >>>> get acquainted with the code if not fix it ;)<br>
>>> >>>><br>
>>> >>>><br>
>>> >>>> On Wed, Jan 15, 2014 at 10:24 PM, George Gastaldi <<br>
>>> <a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a>>wrote:<br>
>>> >>>><br>
>>> >>>>> Hey Ivan,<br>
>>> >>>>><br>
>>> >>>>> We had to remove the colors because the colors were "bleeding" to<br>
>>> the<br>
>>> >>>>> next character. If you could have a look at it, the code is in<br>
>>> >>>>> ShellImpl.createPrompt().<br>
>>> >>>>><br>
>>> >>>>> Pull requests are always more than welcomed. :)<br>
>>> >>>>><br>
>>> >>>>> Em 15/01/2014, às 18:21, "Ivan St. Ivanov" <<br>
>>> <a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>><br>
>>> >>>>> escreveu:<br>
>>> >>>>><br>
>>> >>>>> Hi Stale, folks!<br>
>>> >>>>><br>
>>> >>>>> I just tried the new Forge 2.0 and it works perfectly :)<br>
>>> >>>>><br>
>>> >>>>> I just miss the prompt coloring. In Forge 1 we had different color<br>
>>> for<br>
>>> >>>>> the current directory name if it is inside a project.<br>
>>> >>>>><br>
>>> >>>>> BTW, I see that the new-project command was changed to project-new.<br>
>>> >>>>><br>
>>> >>>>> Cheers,<br>
>>> >>>>> Ivan<br>
>>> >>>>><br>
>>> >>>>><br>
>>> >>>>> On Mon, Jan 13, 2014 at 3:39 AM, George Gastaldi <<br>
>>> <a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a>>wrote:<br>
>>> >>>>><br>
>>> >>>>>> Excellent Stale! Thanks for your help on this.<br>
>>> >>>>>><br>
>>> >>>>>>> Em 12/01/2014, às 23:06, Ståle W Pedersen <<a href="mailto:spederse@redhat.com">spederse@redhat.com</a>><br>
>>> >>>>>> escreveu:<br>
>>> >>>>>>><br>
>>> >>>>>>> hi, ive deployed a new version of 0.46-SNAPSHOT that hopefully<br>
>>> should<br>
>>> >>>>>>> have most of the arrow-key + line redraw bugs fixed.<br>
>>> >>>>>>> - please let me know if it works better other places as well.<br>
>>> >>>>>>><br>
>>> >>>>>>> these issues were introduced back in oct/nov i think (during our<br>
>>> >>>>>> meeting<br>
>>> >>>>>>> in raleigh lincoln :) when we optimized the input and line draw<br>
>>> in æsh.<br>
>>> >>>>>>> - i think its time i get a working windows setup....<br>
>>> >>>>>>><br>
>>> >>>>>>> i havent looked at the path issue so that still needs to be fixed.<br>
>>> >>>>>>> - but ill prioritize the close issue atm.<br>
>>> >>>>>>><br>
>>> >>>>>>> ståle<br>
>>> >>>>>>><br>
>>> >>>>>>>> On 11.01.14 17:10, Lincoln Baxter, III wrote:<br>
>>> >>>>>>>> You can find in maven under:<br>
>>> >>>>>>>><br>
>>> >>>>>>>> org.jboss.aesh:aesh:0.46-SNAPSHOT<br>
>>> >>>>>>>><br>
>>> >>>>>>>> The github repo/org is here: <a href="https://github.com/aeshell/aesh" target="_blank">https://github.com/aeshell/aesh</a><br>
>>> >>>>>>>><br>
>>> >>>>>>>> ~Lincoln<br>
>>> >>>>>>>><br>
>>> >>>>>>>><br>
>>> >>>>>>>> On Sat, Jan 11, 2014 at 3:58 PM, Ståle W Pedersen <<br>
>>> >>>>>> <a href="mailto:spederse@redhat.com">spederse@redhat.com</a>>wrote:<br>
>>> >>>>>>>><br>
>>> >>>>>>>>> hi, ivan it is most likely an æsh bug (which forge uses for<br>
>>> shell<br>
>>> >>>>>>>>> interaction). to quickly debug æsh you could just start a simple<br>
>>> >>>>>> 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<br>
>>> >>>>>> 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<br>
>>> bug<br>
>>> >>>>>> in a<br>
>>> >>>>>>>>> later release with this or it might also be the parsing.<br>
>>> whatever you<br>
>>> >>>>>>>>> find out will no matter help.<br>
>>> >>>>>>>>><br>
>>> >>>>>>>>> regards, ståle<br>
>>> >>>>>>>>><br>
>>> >>>>>>>>>> On 11.01.14 21:18, Ivan St. Ivanov wrote:<br>
>>> >>>>>>>>>> Hi folks,<br>
>>> >>>>>>>>>><br>
>>> >>>>>>>>>> I just created this JIRA:<br>
>>> >>>>>> <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<br>
>>> it. I<br>
>>> >>>>>> just<br>
>>> >>>>>>>>>> need some guidance on where to look. George asked me to run the<br>
>>> >>>>>> unit tests<br>
>>> >>>>>>>>>> and I tried. However, the addon-manager tests failed and I<br>
>>> couldn't<br>
>>> >>>>>> 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<br>
>>> what<br>
>>> >>>>>> we will<br>
>>> >>>>>>>>>>> be working on next few days :)<br>
>>> >>>>>>>>>>><br>
>>> >>>>>>>>>>><br>
>>> >>>>>>>>>>> On Sat, Jan 11, 2014 at 12:40 PM, George Gastaldi <<br>
>>> >>>>>> <a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a><br>
>>> >>>>>>>>>> wrote:<br>
>>> >>>>>>>>>>><br>
>>> >>>>>>>>>>>> Ivan,<br>
>>> >>>>>>>>>>>><br>
>>> >>>>>>>>>>>> Could you open a JIRA with these issues and mark it as<br>
>>> Blocker? We<br>
>>> >>>>>>>>> can't<br>
>>> >>>>>>>>>>>> release 2.0.0.Final unless this is fixed.<br>
>>> >>>>>>>>>>>><br>
>>> >>>>>>>>>>>> Em 08/01/2014, às 11:18, "Ivan St. Ivanov" <<br>
>>> >>>>>> <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<br>
>>> December,<br>
>>> >>>>>>>>> 29th.<br>
>>> >>>>>>>>>>>> The situation was the same with all the previous betas and<br>
>>> alphas.<br>
>>> >>>>>>>>>>>><br>
>>> >>>>>>>>>>>><br>
>>> >>>>>>>>>>>> On Wed, Jan 8, 2014 at 3:13 PM, George Gastaldi <<br>
>>> >>>>>> <a href="mailto:ggastald@redhat.com">ggastald@redhat.com</a><br>
>>> >>>>>>>>>> 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" <<br>
>>> >>>>>> <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<br>
>>> about<br>
>>> >>>>>> the new<br>
>>> >>>>>>>>>>>>> Forge 2 shell. As some of you know, I use Windows (Really?<br>
>>> >>>>>> OK...). So<br>
>>> >>>>>>>>> I<br>
>>> >>>>>>>>>>>>> will be very happy to help you solve the issues besides<br>
>>> merely<br>
>>> >>>>>>>>> reporting<br>
>>> >>>>>>>>>>>>> them:<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>>>>>>>>> * The history doesn't work. That is, when you press up and<br>
>>> down<br>
>>> >>>>>> arrows<br>
>>> >>>>>>>>>>>>> instead of the previous commands, you get this: αH<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>>>>>>>>> * Backspace doesn't work. When I press it, the cursor just<br>
>>> comes<br>
>>> >>>>>> back<br>
>>> >>>>>>>>> to<br>
>>> >>>>>>>>>>>>> the previous position without deleting the character there.<br>
>>> If I<br>
>>> >>>>>> just<br>
>>> >>>>>>>>> write<br>
>>> >>>>>>>>>>>>> something there, the old symbol is overwritten by the new<br>
>>> one,<br>
>>> >>>>>> but at<br>
>>> >>>>>>>>> the<br>
>>> >>>>>>>>>>>>> end after pressing enter it looks like you never entered<br>
>>> anything<br>
>>> >>>>>>>>> after<br>
>>> >>>>>>>>>>>>> pressing backspace. For example:<br>
>>> >>>>>>>>>>>>> 1) I write *new-project --namek*<br>
>>> >>>>>>>>>>>>> 2) I notice the typo and press backspace<br>
>>> >>>>>>>>>>>>> 3) k doesn't get deleted, but I overwrite it with d<br>
>>> >>>>>>>>>>>>> 4) Then I complete my command to look like this:<br>
>>> *new-project<br>
>>> >>>>>>>>> --named<br>
>>> >>>>>>>>>>>>> test*<br>
>>> >>>>>>>>>>>>> 5) Forge's output is: *Project name must be specified.*<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>>>>>>>>> * As you know on windows the full path to a file or<br>
>>> directory is<br>
>>> >>>>>>>>>>>>> <drive-letter>:\<dir1>\<dir2><br>
>>> >>>>>>>>>>>>> 1) If I try to do *cd c:\temp\forge*, Forge blows with<br>
>>> >>>>>> exception:<br>
>>> >>>>>>>>>>>>> org.jboss.forge.addon.resource.ResourceException:<br>
>>> >>>>>> [FileResourceImpl]<br>
>>> >>>>>>>>> can<br>
>>> >>>>>>>>>>>>> have no<br>
>>> >>>>>>>>>>>>> children<br>
>>> >>>>>>>>>>>>> at<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>><br>
>>> org.jboss.forge.addon.resource.AbstractFileResource.getChild(Abstract<br>
>>> >>>>>>>>>>>>> FileResource.java:78)<br>
>>> >>>>>>>>>>>>> at<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>><br>
>>> org.jboss.forge.addon.shell.util.PathspecParser.resolve(PathspecParse<br>
>>> >>>>>>>>>>>>> r.java:232)<br>
>>> >>>>>>>>>>>>> at<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>><br>
>>> org.jboss.forge.addon.shell.commands.CdCommand.execute(CdCommand.java<br>
>>> >>>>>>>>>>>>> :71)<br>
>>> >>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native<br>
>>> >>>>>> Method)<br>
>>> >>>>>>>>>>>>> at<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>><br>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.<br>
>>> >>>>>>>>>>>>> java:57)<br>
>>> >>>>>>>>>>>>> at<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>><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<br>
>>> drive<br>
>>> >>>>>>>>>>>>> letter, e.g. just \<dir1>\<dir2>. It is legal to do it in<br>
>>> >>>>>> Windows,<br>
>>> >>>>>>>>> but thus<br>
>>> >>>>>>>>>>>>> you can't change to a directory located on a different<br>
>>> drive. For<br>
>>> >>>>>>>>> example<br>
>>> >>>>>>>>>>>>> cd \temp\forge will change to c:\temp\forge if you are<br>
>>> currently<br>
>>> >>>>>> in<br>
>>> >>>>>>>>> c:. So<br>
>>> >>>>>>>>>>>>> I tried *cd \temp\forge*, but the result was the same<br>
>>> >>>>>> [exception].<br>
>>> >>>>>>>>>>>>> 3) If I am in the root directory (c:\) and I run *cd<br>
>>> >>>>>> temp\forge*, I<br>
>>> >>>>>>>>>>>>> don't get exception, but ****ERROR*** tempforge\: No such<br>
>>> file or<br>
>>> >>>>>>>>>>>>> directory*. The interesting thing is that I ran that<br>
>>> command by<br>
>>> >>>>>>>>>>>>> pressing tab, i.e. counting on the command completion of the<br>
>>> >>>>>> shell,<br>
>>> >>>>>>>>> which<br>
>>> >>>>>>>>>>>>> obviously works fine.<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>>>>>>>>> I made the cd command work by just running *cd /temp/forge*<br>
>>> >>>>>> (notice<br>
>>> >>>>>>>>>>>>> the forward slashes)<br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>>>>>>>>><br>
>>> >>>>>>>>>>>>> If you wish, I may add these observations as JIRA items,<br>
>>> >>>>>> probably as<br>
>>> >>>>>>>>>>>>> children to this one:<br>
>>> <a href="https://issues.jboss.org/browse/FORGE-1387" target="_blank">https://issues.jboss.org/browse/FORGE-1387</a><br>
>>> >>>>>> .<br>
>>> >>>>>>>>> Bear<br>
>>> >>>>>>>>>>>>> in mind that all the reported features work in Forge 1 even<br>
>>> on<br>
>>> >>>>>>>>> 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><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>
>>> >>>>>>> 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><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>
>>> >>>> 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>
>>> 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>
>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></div></div></blockquote></div><br></div>