[forge-dev] Tests on Windows

[Lincoln Baxter, III]

I've merged the pull requests into master. You might want to try again.

~Lincoln

On Fri, Mar 30, 2012 at 2:34 AM, Koen Aers <koen.aers at gmail.com> wrote:

> Hi Ivan,
>
> I did run the tests from the command line right after deleting the repo. I
> only ran the failing test in Eclipse afterwards to be able to debug and see
> what's going on.
>
> Are you saying that the tests work for you on Windows without the
> mentioned problem and after deleting your repo?
>
> Cheers,
> Koen
>
>
> Op 30-mrt.-2012, om 00:33 heeft Ivan St. Ivanov het volgende geschreven:
>
> Hi Koen,
>
> You run your tests from Eclipse, right? Could you try to run mvn test on
> the command line after deleting your repo? This downloads all the missing
> jars to your local repository and then executes the test. Afterwards it's
> green when run in Eclipse as well.
>
> You may also try updating the maven dependencies form the IDE, but on my
> host it failed with another error - Arquillian can't find a manifest or
> something.
>
> The bottom line is - when you delete the repo - run maven build prior to
> running the test from Eclipse.
>
> Cheers,
> Ivan
>
> P.S. I tested that on Windows 7. Didn't really have the time to try it on
> XP.
>
> On Thu, Mar 29, 2012 at 10:39 AM, Koen Aers <koen.aers at gmail.com> wrote:
>
>> Hi all,
>>
>> I have spent quite some time trying to get the test suite to run on
>> Windows. A very annoying problem is the \r\n sequence to end the lines.
>> However, there is something else…
>>
>> After applying the fixes that gastaldi and myself created the tests ran
>> on my Windows 7 box. There was still a problem with the following test on
>> Windows XP:
>>
>> org.jboss.forge.maven.facets.MavenDependencyFacetTest->testHasDependencyBehavior
>>
>> It turned out that the expected dependency on cdi is not found. I was
>> puzzled why this worked on Windows 7 and not on Windows XP, so I deleted
>> the local Maven repo and behold… it also failed (again) on Windows 7. Don't
>> know if we need to be glad or sad about this though but it seems to be a
>> missing Maven dependency in the repo. Also with a debugger attached I can
>> see a ClassNotFoundException somewhere deep in the callstack (I cannot see
>> exactly where because of the Weld proxies) for the class
>> org.apache.maven.model.building.FileModelSource.
>>
>> Does anybody have any idea or suggestions about this?
>>
>> Cheers,
>> Koen
>> _______________________________________________
>> 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.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120330/018007b7/attachment.html