Hey Bertrand, It worked now.
Can you tell me how it's going to be different if tests are disabled? Thanks & Regards, Nitesh Ambuj -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bertrand Delacretaz Sent: Monday, March 17, 2008 2:57 PM To: [email protected] Subject: Re: Failed Tests Hi, On Mon, Mar 17, 2008 at 9:33 AM, Nitesh Ambuj <[EMAIL PROTECTED]> wrote: > ... junit.framework.ComparisonFailure: null expected:<...2>s1</h2><h3>s2</h3>[] > <h3>s2b</h3><h4>s3<...> but was:<...2>s1</h2><h3>s2</h3>[ > ]... > at > org.apache.sling.apt.parser.internal.SlingAptParserImplTest.testSections(Sli > ngAptParserImplTest.java:122)... What's between [] shows that the test fails because of a newline that's present but not expected, might be a bug in our test code w.r.t windows? For now, you should be able to use mvn clean install -Dmaven.test.skip=true to build, with tests disabled, as a workaround. Did someone successfully run that test under Windows? It's fairly new, so it might be broken on that platform, I didn't test that yet. -Bertrand
