[forge-dev] Forge build back to Stable (Hack away!)
Ivan St. Ivanov
ivan.st.ivanov at gmail.com
Tue Dec 13 15:23:32 EST 2011
OK, it was possible. I uninstalled the VC++ stuff. Then just run forge to
make sure that it fails with the above exception (so that I'm sure it was
removed). Then this is what I got:
C:\Documents and Settings\Ivko>set
FORGE_OPTS="-Dforge.compatibility.IDE=true"
C:\Documents and Settings\Ivko>forge
_____
| ___|__ _ __ __ _ ___
| |_ / _ \| `__/ _` |/ _ \ ←[33m\\←[m
| _| (_) | | | (_| | __/ ←[33m//←[m
|_| \___/|_| \__, |\___|
|___/
Windows? Really? Okay...
[←[31mno project←[m] ←[34mIvko←[m ←[31m$←[m
Cheers,
Ivan
On Tue, Dec 13, 2011 at 10:15 PM, Ivan St. Ivanov
<ivan.st.ivanov at gmail.com>wrote:
> Hi Lincoln,
>
> I think that I was misunderstood. I'm afraid that we cannot install the
> VC++ library automatically, but maybe we can detect whether it's needed to
> be installed. And for that maybe we'll need to write some native code.
> Installing these automatically would be impossible I think, just because
> they are shipped with commercial license (at least I suppose so, but take
> this as speculation only).
>
> I could try the forge_opts stuff, but for that I need to uninstall the
> VC++ libs. I'll see whether that's possible.
>
> Cheers!
> Ivan
>
>
> On Tue, Dec 13, 2011 at 7:01 PM, Lincoln Baxter, III <
> lincolnbaxter at gmail.com> wrote:
>
>> Well, I can speak for Richard. I think he uses XP as his OS of choice ;)
>>
>> I think this would make a good experiment. If creating the DLL (if
>> missing) is something that we can do in the background without ever
>> bothering users, then I think it might be good to do. Do you want to play
>> around with creating a little "environment fixup" abstraction that could be
>> used to do this at forge boot time? Something that can go out and check for
>> various things in the host environment and make sure that things are set up
>> right (and take action to fix them.)
>>
>> Before we worry about updating DLLs, however... Ivan, could you try
>> something for me?
>>
>> Try booting forge with:
>> set FORGE_OPTS="-Dforge.compatibility.IDE=true"
>>
>> Do you get the same crash with the missing DLL?
>>
>> ~Lincoln
>>
>>
>> On Tue, Dec 13, 2011 at 11:27 AM, Ivan St. Ivanov <
>> ivan.st.ivanov at gmail.com> wrote:
>>
>>> Hello! :-)
>>>
>>> OK, maybe you are right about the incorrectness of my first assumption
>>> (that nobody is using XP). But I'm still pretty sure about the second one -
>>> everybody actively using XP has installed the latest version of the VC++
>>> runtime.
>>>
>>> *Koen, Richard*: are you active users of your XP systems where you
>>> caught initially the bug or you are just running Forge on them to check
>>> whether it is running on Windows?
>>>
>>> If we finally decide that we want to go without documentation, then
>>> maybe we can think of some kind of [CDI] advice around the
>>> org.jboss.forge.shell.console.jline.WindowsTerminal.getConsoleMode
>>> method. This can check whether the appropriate version of VC++ runtime is
>>> installed and if not, produce a better message pointing to the MS patch
>>> site than an exception and hanging of Forge. The next question here is how
>>> to implement this check. I'm afraid we have to either use external library
>>> packaged with its own dll, or write the dll by ourselves.
>>>
>>> And now the real question comes: should we bother at all right now? Or
>>> act in the agile way: wait for someone to complain and only then go on and
>>> implement such logic?
>>>
>>> Cheers!
>>> Ivan
>>>
>>> On Tue, Dec 13, 2011 at 4:57 PM, Max Rydahl Andersen <
>>> max.andersen at redhat.com> wrote:
>>>
>>>> > A couple of comments though. Apparently the amount of Windows XP
>>>> users is bigger than the combined amounts of Linux and OSX users, so I it
>>>> would be good problem should probably be fixed one way or another. These
>>>> numbers are really trustworthy as they come from data that Max Andersen is
>>>> collecting on a day to day basis from launched JBoss Tools instances.
>>>>
>>>> They don't really become "really trustworthy" until you go look and see
>>>> of the normal browser access on jboss.org and that is similar: tons of
>>>> Windows XP users. Or as I tend to refer to them "the silent majority" :)
>>>>
>>>> Note since this is the issues I would reckon both Roo and Maven Shell
>>>> would have similar issues since they use jline too.
>>>> Anyone up to verify that ? if they don't then might be some newer/older
>>>> version of jline?
>>>>
>>>> /max
>>>>
>>>>
>>>> >
>>>> > AFAIK none of the seasoned forge contributors is *using* XP. But as
>>>> the numbers above indicate it is still good to once in a while test on XP
>>>> and make sure it continues to run on that platform. IIRC XP is end of life
>>>> in 2014 so we will need to put up with it for some more time. ;-)
>>>> >
>>>> > Cheers,
>>>> > Koen
>>>> >
>>>> > Op 13-dec.-2011, om 00:13 heeft Ivan St. Ivanov het volgende
>>>> geschreven:
>>>> >
>>>> >> I think that we may go with "asking people to install DLLs".
>>>> >>
>>>> >> 1) I don't know too many Windows XP users (I come from a country
>>>> where 99% of the people are using Windows)
>>>> >> 2) Even if there are such users, they should have installed this
>>>> package anyway, because a lot of other programs require it as well (think
>>>> of it as a JRE, but for MS library based applications)
>>>> >>
>>>> >> What is more interesting to me is how come two of the seasoned forge
>>>> contributors are still using XP ;-)
>>>> >>
>>>> >> On Tue, Dec 13, 2011 at 12:57 AM, Lincoln Baxter, III <
>>>> lincolnbaxter at gmail.com> wrote:
>>>> >> INTERESTING!
>>>> >>
>>>> >> I wonder why this is happening. I now seem to remember an issue like
>>>> this from a *long* time ago. Not sure what the best solution to the problem
>>>> is... asking people to install DLLs is not a very nice experience.
>>>> >>
>>>> >> Good thing: Using Forge in Eclipse does not suffer from this problem.
>>>> >>
>>>> >> ~Lincoln
>>>> >>
>>>> >>
>>>> >> On Mon, Dec 12, 2011 at 5:53 PM, Ivan St. Ivanov <
>>>> ivan.st.ivanov at gmail.com> wrote:
>>>> >> Hi folks!
>>>> >>
>>>> >> I installed Windows XP on a VirtualBox instance. Then installed Java
>>>> and Maven and extracted the latest dev build of forge. I started it and got
>>>> the following exception (pasting the most relevant part):
>>>> >>
>>>> >> Exception in thread "Thread-2"
>>>> javax.enterprise.event.ObserverException
>>>> >> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>>> >>
>>>> >> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
>>>> >> orAccessorImpl.java:39)
>>>> >> at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
>>>> >> onstructorAccessorImpl.java:27)
>>>> >> at
>>>> java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>>> >> ....
>>>> >> Caused by: java.lang.NoClassDefFoundError: Could not initialize
>>>> class org.fusesource.jansi.internal.Kernel32
>>>> >> at
>>>> org.fusesource.jansi.internal.WindowsSupport.getConsoleMode(WindowsSu
>>>> >> pport.java:48)
>>>> >> at
>>>> org.jboss.forge.shell.console.jline.WindowsTerminal.getConsoleMode(Wi
>>>> >> ndowsTerminal.java:257)
>>>> >> at
>>>> org.jboss.forge.shell.console.jline.WindowsTerminal.init(WindowsTermi
>>>> >> nal.java:94)
>>>> >>
>>>> >>
>>>> >> So I searched Google for the NoClassDefFoundError and came upon this
>>>> link:
>>>> >>
>>>> >> http://fusesource.com/forums/thread.jspa?messageID=10985
>>>> >>
>>>> >> This seemed to be the clue:
>>>> >>
>>>> >> The problem is missing dll from Visual C++ libraries on the windows
>>>> XP. I follow the following instruction :
>>>> http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5582
>>>> >>
>>>> >> And now, it's good
>>>> >>
>>>> >> I installed the VC++ libraries from the above link and forge
>>>> eventually worked :-)
>>>> >>
>>>> >> Could you try it?
>>>> >>
>>>> >> Cheers,
>>>> >> Ivan
>>>> >>
>>>> >>
>>>> >> On Wed, Dec 7, 2011 at 11:33 AM, Ivan St. Ivanov <
>>>> ivan.st.ivanov at gmail.com> wrote:
>>>> >> Hi!
>>>> >>
>>>> >> Unfortunately, I am using Windows 7. At home I have one Windows
>>>> Vista, but no XP. I can create a VirtualBox instance and install XP inside,
>>>> but it will take me some time.
>>>> >>
>>>> >> BTW, if it is really hanging, can you (Richard or Koen) press
>>>> Ctrl+Break and see whether some thread is causing this?
>>>> >>
>>>> >> Cheers!
>>>> >> Ivan
>>>> >>
>>>> >>
>>>> >> On Wed, Dec 7, 2011 at 6:40 AM, Richard Kennard <
>>>> richard at kennardconsulting.com> wrote:
>>>> >> Yeah it never starts up.
>>>> >>
>>>> >> To be absolutely clear:
>>>> >>
>>>> >> 1. It does not crash or die. There is no stack trace or return to
>>>> the command prompt.
>>>> >> 2. It runs in the sense that you get a flashing cursor that just
>>>> sits there. But it does not display the 'Forge' ASCII art or anything
>>>> >> 3. It is evidently waiting on input, because if you hit return the
>>>> cursor moves down a line. But only once. Pressing return a second time does
>>>> nothing
>>>> >>
>>>> >> On 7/12/2011 3:31 PM, Lincoln Baxter, III wrote:
>>>> >> > I think they mean that it never starts up, which is very strange
>>>> to me.
>>>> >> >
>>>> >> > Happy holiday! I haven't actually heard of that one before
>>>> (ignorant me.) But have fun :)
>>>> >> >
>>>> >> > I do want to work on the startup time, but this "never starting"
>>>> behavior is very strange and I can't reproduce it on windows 7.
>>>> >> >
>>>> >> > Hopefully Koen will be able to. (Unless you have access to a
>>>> windows 95 box?)
>>>> >> >
>>>> >> > ~Lincoln
>>>> >> >
>>>> >> > On Tue, Dec 6, 2011 at 4:28 PM, Ivan St. Ivanov <
>>>> ivan.st.ivanov at gmail.com <mailto:ivan.st.ivanov at gmail.com>> wrote:
>>>> >> >
>>>> >> > Hi Lincoln, folks!
>>>> >> >
>>>> >> > Sure I will help. However, I wonder a couple of things:
>>>> >> >
>>>> >> > 1) What do you mean by hanging? Yes, Forge takes some 5-10
>>>> seconds to start, but it finally starts. So do you aim at ~2 seconds start
>>>> or maybe at
>>>> >> > Koen's and Richard's computers it never starts at all
>>>> >> >
>>>> >> > 2) When I start the debug session, should I put somewhere
>>>> breakpoints? If yes, where?
>>>> >> >
>>>> >> > Cheers,
>>>> >> > Ivan
>>>> >> >
>>>> >> > P.S. Sorry, but I'll do that tomorrow! Today is St. Nicolas's
>>>> day here in Bulgaria (and I believe in the whole Christian world) and right
>>>> now I am
>>>> >> > celebrating with a friend of mine his name's day ;-)
>>>> >> >
>>>> >> >
>>>> >> > On Tue, Dec 6, 2011 at 11:07 PM, Lincoln Baxter, III <
>>>> lincolnbaxter at gmail.com <mailto:lincolnbaxter at gmail.com>> wrote:
>>>> >> >
>>>> >> > Awesome, thanks koen.
>>>> >> >
>>>> >> > Ivan,
>>>> >> >
>>>> >> > Could I ask you a favor? Could you follow the debugging
>>>> instructions in FORGE-400 (comments) and try to find our where Forge is
>>>> hanging at
>>>> >> > runtime? This would help me a *lot* since I cannot get
>>>> access to an XP machine right now.
>>>> >> >
>>>> >> > ~Lincoln
>>>> >> >
>>>> >> >
>>>> >> > On Tue, Dec 6, 2011 at 3:44 AM, Koen Aers <
>>>> koen.aers at gmail.com <mailto:koen.aers at gmail.com>> wrote:
>>>> >> >
>>>> >> > I have created
>>>> https://issues.jboss.org/browse/FORGE-400.
>>>> >> >
>>>> >> > Cheers,
>>>> >> > Koen
>>>> >> >
>>>> >> > Op 6-dec.-2011, om 09:20 heeft Richard Kennard het
>>>> volgende geschreven:
>>>> >> >
>>>> >> > >> on Windows 7: run hangs right after startup
>>>> >> > >
>>>> >> > > Yes, I can confirm this.
>>>> >> > >
>>>> >> > > Richard.
>>>> >> > >
>>>> >> > > On 6/12/2011 6:16 PM, Koen Aers wrote:
>>>> >> > >> This is very strange. I didn't go into the details
>>>> but while running the tests on XP I had to use the "line.separator"
>>>> property because
>>>> >> > the output in the
>>>> >> > >> test contained "\r\n" and not "\n".
>>>> >> > >> I'm confused now…
>>>> >> > >>
>>>> >> > >> Btw, I don't know what's happening but I can's seem
>>>> to build trunk on any other platform than OSX.
>>>> >> > >>
>>>> >> > >> - on XP: build as well as run hang
>>>> >> > >> - on Windows 7: build fails with compilation error,
>>>> run hangs right after startup
>>>> >> > >> - on Fedora 16: build fails with (another)
>>>> compilation error, run is ok
>>>> >> > >>
>>>> >> > >> I tried the runs with a snapshot build that I did
>>>> on OSX. I'll create a JIRA issue to track these problems.
>>>> >> > >>
>>>> >> > >> Cheers,
>>>> >> > >> Koen
>>>> >> > >>
>>>> >> > >> Op 5-dec.-2011, om 22:24 heeft Ivan St. Ivanov het
>>>> volgende geschreven:
>>>> >> > >>
>>>> >> > >>> Hi folks,
>>>> >> > >>>
>>>> >> > >>> Richard, thanks a lot for the hint! After
>>>> downloading the latest version my source compiles.
>>>> >> > >>>
>>>> >> > >>> However, now I get an error in the test:
>>>> JavaClassTest::testFormattingIsNotChanged. The problem is in the asserts
>>>> that check whether the
>>>> >> > output contains
>>>> >> > >>> Telephone + line.separator + {. The next assert,
>>>> which also has the line.separator inside, fails too. I am running on
>>>> Windows. And there
>>>> >> > line.separator
>>>> >> > >>> is \r\n. However, in the output we get just \n.
>>>> Which is fine on Mac or UNIX.
>>>> >> > >>>
>>>> >> > >>> If I change the asserts like this (replace
>>>> line.separator with \n):
>>>> >> > >>>
>>>> >> > >>> assertTrue(output.contains(
>>>> >> > >>> "Telephone\n{"));
>>>> >> > >>> assertTrue(output.contains(
>>>> >> > >>> ")\n {"));
>>>> >> > >>>
>>>> >> > >>> ...it works on Windows.
>>>> >> > >>>
>>>> >> > >>> Of course it's better to fix this in the code, but
>>>> I saw that the toString method uses the stuff from Eclipse
>>>> >> > (org.eclipse.jface.text.Document,
>>>> >> > >>> org.eclipse.text.edits.TextEdit,
>>>> org.eclipse.jdt.core.dom.CompilationUnit). So I'm not sure whether we can
>>>> do anything there. Unless some
>>>> >> > of you has
>>>> >> > >>> commit permissions in Eclipse or my observations
>>>> are wrong :-)
>>>> >> > >>>
>>>> >> > >>> What do you think?
>>>> >> > >>>
>>>> >> > >>> Cheers!
>>>> >> > >>> Ivan
>>>> >> > >>>
>>>> >> > >>> P.S. If I change the test like above (with \n
>>>> instead of line.separator), the maven build is successful
>>>> >> > >>>
>>>> >> > >>> On Sun, Dec 4, 2011 at 11:37 PM, Richard Kennard <
>>>> richard at kennardconsulting.com <mailto:richard at kennardconsulting.com>
>>>> >> > <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com>>> wrote:
>>>> >> > >>>
>>>> >> > >>> Ivan,
>>>> >> > >>>
>>>> >> > >>> Apologies. Forge is currently building against a
>>>> Metawidget snapshot, and that snapshot is still changing. You will need to
>>>> pull the
>>>> >> > latest Forge
>>>> >> > >>> build in
>>>> >> > >>> order to get the changes (HtmlTableLayout has
>>>> become HtmlPanelGridLayout).
>>>> >> > >>>
>>>> >> > >>> Regards,
>>>> >> > >>>
>>>> >> > >>> Richard.
>>>> >> > >>>
>>>> >> > >>> On 5/12/2011 1:58 AM, Ivan St. Ivanov wrote:
>>>> >> > >>>> Hi guys!
>>>> >> > >>>>
>>>> >> > >>>> I did not pull or merge anything since my last
>>>> successful build (or at least I think so). And now I have a compilation
>>>> problem:
>>>> >> > >>>>
>>>> >> > >>>> [ERROR]
>>>> \projects\seamforge\core\scaffold-faces\src\main\java\org\jboss\forge\scaffold\faces\FacesScaffold.java:[87,60]
>>>> >> > >>>> cannot find symbol
>>>> >> > >>>> symbol : class HtmlTableLayout
>>>> >> > >>>> location: package
>>>> org.metawidget.statically.faces.component.html.layout
>>>> >> > >>>>
>>>> >> > >>>> [ERROR]
>>>> \projects\seamforge\core\scaffold-faces\src\main\java\org\jboss\forge\scaffold\faces\FacesScaffold.java:[354,48]
>>>> >> > >>>> cannot find symbol
>>>> >> > >>>> symbol : class HtmlTableLayout
>>>> >> > >>>> location: class
>>>> org.jboss.forge.scaffold.faces.FacesScaffold
>>>> >> > >>>>
>>>> >> > >>>>
>>>> >> > >>>> The HtmlTableLayout class is in the
>>>> org.metawidget.statically.faces.component.html.layout package coming from
>>>> the
>>>> >> > >>> org.metawidget.modules/metawidget-all
>>>> >> > >>>> dependency (version 1.35-SNAPSHOT). There is
>>>> really no such class in the metawidget library. I went on to check the
>>>> jboss maven
>>>> >> > repository. The class
>>>> >> > >>>> HTMLTableLayout Indeed existed in older versions
>>>> of the jar. However, it's not there in latest ones (those after 1st
>>>> December).
>>>> >> > >>>>
>>>> >> > >>>> Does anybody else have the same problem?
>>>> >> > >>>>
>>>> >> > >>>> Thanks,
>>>> >> > >>>> Ivan
>>>> >> > >>>>
>>>> >> > >>>> On Thu, Dec 1, 2011 at 1:06 PM, Koen Aers <
>>>> koen.aers at gmail.com <mailto:koen.aers at gmail.com> <mailto:
>>>> koen.aers at gmail.com
>>>> >> > <mailto:koen.aers at gmail.com>> <mailto:
>>>> koen.aers at gmail.com <mailto:koen.aers at gmail.com>
>>>> >> > >>> <mailto:koen.aers at gmail.com <mailto:
>>>> koen.aers at gmail.com>>>> wrote:
>>>> >> > >>>>
>>>> >> > >>>> After fixing the failing test on XP, another
>>>> problem shows up…
>>>> >> > >>>>
>>>> >> > >>>> The test 'ValidationFacetTest' in
>>>> 'forge-javaee-impl' hangs while initializing the fixture.
>>>> >> > >>>>
>>>> >> > >>>> More in detail, the call
>>>> 'beanManager.fireEvent(new Startup())' in the 'beforeTest()' method of the
>>>> class
>>>> >> > 'SingletonAbstractShellTest.java' never
>>>> >> > >>>> returns.
>>>> >> > >>>>
>>>> >> > >>>> I have no clue as to what might be the cause of
>>>> this. Any suggestions welcome.
>>>> >> > >>>>
>>>> >> > >>>> Cheers,
>>>> >> > >>>> Koen
>>>> >> > >>>>
>>>> >> > >>>> Op 1-dec.-2011, om 09:15 heeft Ivan St. Ivanov
>>>> het volgende geschreven:
>>>> >> > >>>>
>>>> >> > >>>>> Hi,
>>>> >> > >>>>>
>>>> >> > >>>>> I does hang for ~5 seconds. Not sure if that is
>>>> problematic. But Beta 3 has the same behavior.
>>>> >> > >>>>>
>>>> >> > >>>>> Once it is started I don't see any delays
>>>> (created new project, setup persistence, added an entity and a field).
>>>> >> > >>>>>
>>>> >> > >>>>> Cheers!
>>>> >> > >>>>> Ivan
>>>> >> > >>>>>
>>>> >> > >>>>> On Thu, Dec 1, 2011 at 1:10 AM, Richard Kennard <
>>>> richard at kennardconsulting.com <mailto:richard at kennardconsulting.com>
>>>> >> > <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com>>
>>>> >> > >>> <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com> <mailto:richard at kennardconsulting.com
>>>> >> > <mailto:richard at kennardconsulting.com>>>> wrote:
>>>> >> > >>>>>
>>>> >> > >>>>> But does it run okay? For me, it kept hanging at
>>>> the command prompt after I typed 'bin/forge'.
>>>> >> > >>>>>
>>>> >> > >>>>> Richard.
>>>> >> > >>>>>
>>>> >> > >>>>> On 1/12/2011 10:08 AM, Ivan St. Ivanov wrote:
>>>> >> > >>>>>> Maven build is successful on Windows 7 :-)
>>>> >> > >>>>>>
>>>> >> > >>>>>> On Wed, Nov 30, 2011 at 5:13 PM, Keith Babo <
>>>> kbabo at redhat.com <mailto:kbabo at redhat.com> <mailto:kbabo at redhat.com
>>>> >> > <mailto:kbabo at redhat.com>> <mailto:kbabo at redhat.com<mailto:
>>>> kbabo at redhat.com> <mailto:kbabo at redhat.com <mailto:kbabo at redhat.com>>>
>>>> >> > >>> <mailto:kbabo at redhat.com <mailto:kbabo at redhat.com>
>>>> <mailto:kbabo at redhat.com <mailto:kbabo at redhat.com>> <mailto:
>>>> kbabo at redhat.com
>>>> >> > <mailto:kbabo at redhat.com> <mailto:kbabo at redhat.com<mailto:
>>>> kbabo at redhat.com>>>>>
>>>> >> > >>>>> wrote:
>>>> >> > >>>>>>
>>>> >> > >>>>>>
>>>> >> > >>>>>> You could always spin up a job on the JBoss
>>>> Jenkins server to build this on Windows for you ….
>>>> >> > >>>>>>
>>>> >> > >>>>>> On Nov 30, 2011, at 9:49 AM, Lincoln Baxter,
>>>> III wrote:
>>>> >> > >>>>>>
>>>> >> > >>>>>>> Hey Koen,
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> Could I ask you to look in to this? I am not
>>>> at a place where I have access to windows, and I don't see that error on
>>>> OSX.
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> Thanks!
>>>> >> > >>>>>>> ~Lincoln
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> On Wed, Nov 30, 2011 at 7:12 AM, Koen Aers <
>>>> koen.aers at gmail.com <mailto:koen.aers at gmail.com> <mailto:
>>>> koen.aers at gmail.com
>>>> >> > <mailto:koen.aers at gmail.com>> <mailto:
>>>> koen.aers at gmail.com <mailto:koen.aers at gmail.com>
>>>> >> > >>> <mailto:koen.aers at gmail.com <mailto:
>>>> koen.aers at gmail.com>>> <mailto:koen.aers at gmail.com <mailto:
>>>> koen.aers at gmail.com>
>>>> >> > <mailto:koen.aers at gmail.com <mailto:
>>>> koen.aers at gmail.com>>
>>>> >> > >>>>> <mailto:koen.aers at gmail.com <mailto:
>>>> koen.aers at gmail.com> <mailto:koen.aers at gmail.com <mailto:
>>>> koen.aers at gmail.com>>>>> wrote:
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> I was able to build, test and run without
>>>> issues on OSX. On Windows (XP) the build stopped after the following
>>>> failing test. I didn't
>>>> >> > >>>>>>> investigate any further.
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> Cheers,
>>>> >> > >>>>>>> Koen
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> -------------------------------------------------------------------------------
>>>> >> > >>>>>>> Test set:
>>>> org.jboss.forge.test.parser.java.JavaClassTest
>>>> >> > >>>>>>>
>>>> -------------------------------------------------------------------------------
>>>> >> > >>>>>>> Tests run: 25, Failures: 1, Errors: 0,
>>>> Skipped: 0, Time elapsed: 0.078 sec <<< FAILURE!
>>>> >> > >>>>>>>
>>>> testFormattingIsNotChanged(org.jboss.forge.test.parser.java.JavaClassTest)
>>>> Time elapsed: 0.015 sec <<< FAILURE!
>>>> >> > >>>>>>> java.lang.AssertionError:
>>>> >> > >>>>>>> at org.junit.Assert.fail(Assert.java:91)
>>>> >> > >>>>>>> at org.junit.Assert.assertTrue(Assert.java:43)
>>>> >> > >>>>>>> at org.junit.Assert.assertTrue(Assert.java:54)
>>>> >> > >>>>>>> at
>>>> org.jboss.forge.test.parser.java.JavaClassTest.testFormattingIsNotChanged(JavaClassTest.java:77)
>>>> >> > >>>>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> >> > >>>>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> >> > >>>>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> >> > >>>>>>> at
>>>> java.lang.reflect.Method.invoke(Method.java:597)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>>>> >> > >>>>>>> at
>>>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>>>> >> > >>>>>>> at
>>>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>>>> >> > >>>>>>> at
>>>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>>>> >> > >>>>>>> at
>>>> org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>>>> >> > >>>>>>> at
>>>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
>>>> >> > >>>>>>> at
>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
>>>> >> > >>>>>>> at
>>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102)
>>>> >> > >>>>>>> at
>>>> org.apache.maven.surefire.Surefire.run(Surefire.java:180)
>>>> >> > >>>>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> >> > >>>>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> >> > >>>>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> >> > >>>>>>> at
>>>> java.lang.reflect.Method.invoke(Method.java:597)
>>>> >> > >>>>>>> at
>>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
>>>> >> > >>>>>>> at
>>>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> On Wed, Nov 30, 2011 at 11:10 AM, Richard
>>>> Kennard <richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com>
>>>> >> > <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com>>
>>>> >> > >>> <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com> <mailto:richard at kennardconsulting.com
>>>> >> > <mailto:richard at kennardconsulting.com>>>
>>>> >> > >>>>> <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com> <mailto:richard at kennardconsulting.com
>>>> >> > <mailto:richard at kennardconsulting.com>> <mailto:
>>>> richard at kennardconsulting.com <mailto:richard at kennardconsulting.com>
>>>> >> > >>> <mailto:richard at kennardconsulting.com <mailto:
>>>> richard at kennardconsulting.com>>>>> wrote:
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> Lincoln,
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> The build seems to run, and there are no
>>>> lingering test failures, but on Windows the distribution fails to start up?
>>>> It just hangs at the
>>>> >> > >>>>>>> command prompt,
>>>> >> > >>>>>>> without printing 'Forge' in ASCII text or
>>>> anything. It appears to be waiting for keyboard input, as if I press ENTER
>>>> the cursor moves
>>>> >> > down
>>>> >> > >>>>>>> once, but then
>>>> >> > >>>>>>> it too stops.
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> I have grown so used to Forge telling me I'm
>>>> an idiot for running Windows, but now it won't even do that :)
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> Regards,
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> Richard.
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> On 30/11/2011 9:07 PM, Max Rydahl Andersen
>>>> wrote:
>>>> >> > >>>>>>>> What was the problem in the end ?
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>> My guess was a memory leak in forge or the
>>>> testsuite - did I win ?
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>> /max
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>> On Nov 29, 2011, at 22:16, Lincoln Baxter,
>>>> III wrote:
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>>> Please feel free to run the full build on
>>>> any operating system, without the aggravation of lingering test failures!
>>>> >> > >>>>>>>>>
>>>> >> > >>>>>>>>> --
>>>> >> > >>>>>>>>> Lincoln Baxter, III
>>>> >> > >>>>>>>>> http://ocpsoft.com <http://ocpsoft.com/> <
>>>> http://ocpsoft.com/> <http://ocpsoft.com/>
>>>> >> > >>>>>>>>> http://scrumshark.com <
>>>> http://scrumshark.com/> <http://scrumshark.com/> <
>>>> http://scrumshark.com/>
>>>> >> > >>>>>>>>> "Keep it Simple"
>>>> >> > >>>>>>>>>
>>>> _______________________________________________
>>>> >> > >>>>>>>>> forge-dev mailing list
>>>> >> > >>>>>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>> <mailto:
>>>> forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org> <mailto:
>>>> forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>>>>
>>>> >> > >>>>>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>>>> /max
>>>> >> > >>>>>>>> http://about.me/maxandersen
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>>
>>>> _______________________________________________
>>>> >> > >>>>>>>> forge-dev mailing list
>>>> >> > >>>>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>> <mailto:
>>>> forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org> <mailto:
>>>> forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>>>>
>>>> >> > >>>>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> _______________________________________________
>>>> >> > >>>>>>> forge-dev mailing list
>>>> >> > >>>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>> <mailto:
>>>> forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org> <mailto:
>>>> forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>>>>
>>>> >> > >>>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> _______________________________________________
>>>> >> > >>>>>>> forge-dev mailing list
>>>> >> > >>>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>> <mailto:
>>>> forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org> <mailto:
>>>> forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>>>>
>>>> >> > >>>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>>
>>>> >> > >>>>>>> --
>>>> >> > >>>>>>> Lincoln Baxter, III
>>>> >> > >>>>>>> http://ocpsoft.com <http://ocpsoft.com/> <
>>>> http://ocpsoft.com/> <http://ocpsoft.com/>
>>>> >> > >>>>>>> http://scrumshark.com <http://scrumshark.com/>
>>>> <http://scrumshark.com/> <http://scrumshark.com/>
>>>> >> > >>>>>>> "Keep it Simple"
>>>> >> > >>>>>>> _______________________________________________
>>>> >> > >>>>>>> forge-dev mailing list
>>>> >> > >>>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>> <mailto:
>>>> forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org> <mailto:
>>>> forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>>>>
>>>> >> > >>>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>>
>>>> >> > >>>>>>
>>>> >> > >>>>>> _______________________________________________
>>>> >> > >>>>>> forge-dev mailing list
>>>> >> > >>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>> <mailto:
>>>> forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org> <mailto:
>>>> forge-dev at lists.jboss.org
>>>> >> > <mailto:forge-dev at lists.jboss.org>>>>
>>>> >> > >>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>>
>>>> >> > >>>>>>
>>>> >> > >>>>>>
>>>> >> > >>>>>>
>>>> >> > >>>>>> _______________________________________________
>>>> >> > >>>>>> forge-dev mailing list
>>>> >> > >>>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>
>>>> >> > >>>>> _______________________________________________
>>>> >> > >>>>> forge-dev mailing list
>>>> >> > >>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>>
>>>> >> > >>>>>
>>>> >> > >>>>> _______________________________________________
>>>> >> > >>>>> forge-dev mailing list
>>>> >> > >>>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>
>>>> >> > >>>>
>>>> >> > >>>> _______________________________________________
>>>> >> > >>>> forge-dev mailing list
>>>> >> > >>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>>
>>>> >> > >>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>>
>>>> >> > >>>>
>>>> >> > >>>>
>>>> >> > >>>>
>>>> >> > >>>> _______________________________________________
>>>> >> > >>>> forge-dev mailing list
>>>> >> > >>>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > >>>>
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>
>>>> >> > >>> _______________________________________________
>>>> >> > >>> forge-dev mailing list
>>>> >> > >>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > >>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>>
>>>> >> > >>>
>>>> >> > >>> _______________________________________________
>>>> >> > >>> forge-dev mailing list
>>>> >> > >>> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org> <mailto:forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>>
>>>> >> > >>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >>
>>>> >> > >>
>>>> >> > >>
>>>> >> > >> _______________________________________________
>>>> >> > >> forge-dev mailing list
>>>> >> > >> forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>
>>>> >> > >> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> > >
>>>> >> > > _______________________________________________
>>>> >> > > forge-dev mailing list
>>>> >> > > forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>
>>>> >> > > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > forge-dev mailing list
>>>> >> > forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>
>>>> >> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Lincoln Baxter, III
>>>> >> > http://ocpsoft.com
>>>> >> > http://scrumshark.com
>>>> >> > "Keep it Simple"
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > forge-dev mailing list
>>>> >> > forge-dev at lists.jboss.org <mailto:
>>>> forge-dev at lists.jboss.org>
>>>> >> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > forge-dev mailing list
>>>> >> > forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>>>> >> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Lincoln Baxter, III
>>>> >> > http://ocpsoft.com
>>>> >> > http://scrumshark.com
>>>> >> > "Keep it Simple"
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > forge-dev mailing list
>>>> >> > forge-dev at lists.jboss.org
>>>> >> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >>
>>>> >> _______________________________________________
>>>> >> forge-dev mailing list
>>>> >> forge-dev at lists.jboss.org
>>>> >> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >>
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> forge-dev mailing list
>>>> >> forge-dev at lists.jboss.org
>>>> >> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Lincoln Baxter, III
>>>> >> http://ocpsoft.com
>>>> >> http://scrumshark.com
>>>> >> "Keep it Simple"
>>>> >>
>>>> >> _______________________________________________
>>>> >> forge-dev mailing list
>>>> >> forge-dev at lists.jboss.org
>>>> >> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> forge-dev mailing list
>>>> >> forge-dev at lists.jboss.org
>>>> >> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>> >
>>>> > _______________________________________________
>>>> > forge-dev mailing list
>>>> > forge-dev at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> forge-dev mailing list
>>>> forge-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>>
>>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.com
>> http://scrumshark.com
>> "Keep it Simple"
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20111213/f5470c24/attachment-0001.html
More information about the forge-dev
mailing list