You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Ersin Er <er...@gmail.com> on 2007/06/25 14:47:54 UTC
[Build] Maven 2.0.7 released, should we upgrade?
http://maven.apache.org/release-notes.html
--
Ersin Er
R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
http://www.cs.hacettepe.edu.tr
Committer and PMC Member of The Apache Directory Project
http://directory.apache.org
Re: [Build] Maven 2.0.7 released, should we upgrade?
Posted by Christine Koppelt <ch...@googlemail.com>.
Hi Markus,
you are completly right. I have updated the script.
Thanks for the hint!
Christine
<snip/>
> Another error was thrown when I tried to start the server without the
> installation from within apacheds/server-main using apacheds.bat. The
> error message was:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> DS\apachds15\apacheds-trunk\apacheds\server-main/log4j/properties
>
> Reason for this is that the start script was called from within a
> directory containing whitespaces. The full directory is:
> D:\_Developer\Apache DS\apachds15\apacheds-trunk
>
> To prevent the script from running into this error the following
> change is done in apacheds.bat file:
> before:
> java -Dlog4j.configuration=file:///%cd%/log4j.properties -jar
> target/apacheds-server-main-1.5.1-SNAPSHOT-app.jar server.xml
>
> after:
> java -Dlog4j.configuration="file:///%cd%/log4j.properties" -jar
> target/apacheds-server-main-1.5.1-SNAPSHOT-app.jar server.xml
>
> enclose the log4j.configuration switch with "".
>
> Greetings
> Markus
>
>
>
>
> Zitat von Emmanuel Lecharny <el...@gmail.com>:
>
> > Hi,
> >
> > does it work fine ?
> >
> > If so, let's just switch
> >
> >
> > On 6/25/07, Ersin Er <er...@gmail.com> wrote:
> >> http://maven.apache.org/release-notes.html
> >>
> >> --
> >> Ersin Er
> >>
> >> R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
> >> http://www.cs.hacettepe.edu.tr
> >>
> >> Committer and PMC Member of The Apache Directory Project
> >> http://directory.apache.org
> >>
> >
> >
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com
>
>
>
> --
> WEBUNITY - Internet, Consulting, Neue Medien
> Markus Pohle (SCJP)
>
> GPG Public Key Block available at:
> http://www.webunity.de/markus.pohle@webunity.de.txt
>
>
>
Re: [Build] Maven 2.0.7 released, should we upgrade?
Posted by Emmanuel Lecharny <el...@gmail.com>.
Thanks Markus !
FYI, this pb with PersistentSearch is something which only happens
from time to time. As we are waiting for a certain amount of time for
the result to be returned, we something get the wrong result, for
unknown reasons...
One more thing to investigate...
Could you fill a JIRA with this problem, if you successfully reproduce
it on a regular basis ?
This would be just great !
Thanks a lot Markus !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Build] Maven 2.0.7 released, should we upgrade?
Posted by Markus Pohle <ma...@webunity.de>.
Hi All,
checked it out on Windows XP SP2 with Maven 2.0.7 and JDK 1.5.0_10 and
built the trunks, built the installers, did the integration tests and
also built the eclipse files. All run fine, except for one failure in
integration tests. It says:
-------------------------------------------------------------------------------
Test set: org.apache.directory.server.PersistentSearchTest
-------------------------------------------------------------------------------
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
38.484 sec <<< FAILURE!
testPsearchAbandon(org.apache.directory.server.PersistentSearchTest)
Time elapsed: 2.938 sec <<< FAILURE!
junit.framework.ComparisonFailure: expected:<...Tori Amos> but
was:<...Jack Black>
at junit.framework.Assert.assertEquals(Assert.java:81)
at junit.framework.Assert.assertEquals(Assert.java:87)
at
org.apache.directory.server.PersistentSearchTest.testPsearchAbandon(PersistentSearchTest.java:609)
at
org.apache.directory.server.PersistentSearchTest.testPsearchAbandon(PersistentSearchTest.java:609)
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:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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:585)
at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:163)
at org.apache.maven.surefire.Surefire.run(Surefire.java:84)
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:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:244)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:814)
Another error was thrown when I tried to start the server without the
installation from within apacheds/server-main using apacheds.bat. The
error message was:
Exception in thread "main" java.lang.NoClassDefFoundError:
DS\apachds15\apacheds-trunk\apacheds\server-main/log4j/properties
Reason for this is that the start script was called from within a
directory containing whitespaces. The full directory is:
D:\_Developer\Apache DS\apachds15\apacheds-trunk
To prevent the script from running into this error the following
change is done in apacheds.bat file:
before:
java -Dlog4j.configuration=file:///%cd%/log4j.properties -jar
target/apacheds-server-main-1.5.1-SNAPSHOT-app.jar server.xml
after:
java -Dlog4j.configuration="file:///%cd%/log4j.properties" -jar
target/apacheds-server-main-1.5.1-SNAPSHOT-app.jar server.xml
enclose the log4j.configuration switch with "".
Greetings
Markus
Zitat von Emmanuel Lecharny <el...@gmail.com>:
> Hi,
>
> does it work fine ?
>
> If so, let's just switch
>
>
> On 6/25/07, Ersin Er <er...@gmail.com> wrote:
>> http://maven.apache.org/release-notes.html
>>
>> --
>> Ersin Er
>>
>> R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
>> http://www.cs.hacettepe.edu.tr
>>
>> Committer and PMC Member of The Apache Directory Project
>> http://directory.apache.org
>>
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
--
WEBUNITY - Internet, Consulting, Neue Medien
Markus Pohle (SCJP)
GPG Public Key Block available at:
http://www.webunity.de/markus.pohle@webunity.de.txt
Re: [Build] Maven 2.0.7 released, should we upgrade?
Posted by Chris Custine <ch...@gmail.com>.
Everything seems to work for me.
Chris
On 6/25/07, Ersin Er <er...@gmail.com> wrote:
>
> It's working fine for building 1.5 trunks and integration tests.
>
> On 6/25/07, Emmanuel Lecharny <el...@gmail.com> wrote:
> > Hi,
> >
> > does it work fine ?
> >
> > If so, let's just switch
> >
> >
> > On 6/25/07, Ersin Er <er...@gmail.com> wrote:
> > > http://maven.apache.org/release-notes.html
> > >
> > > --
> > > Ersin Er
> > >
> > > R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe
> University
> > > http://www.cs.hacettepe.edu.tr
> > >
> > > Committer and PMC Member of The Apache Directory Project
> > > http://directory.apache.org
> > >
> >
> >
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com
> >
>
>
> --
> Ersin Er
>
> R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe
> University
> http://www.cs.hacettepe.edu.tr
>
> Committer and PMC Member of The Apache Directory Project
> http://directory.apache.org
>
Re: [Build] Maven 2.0.7 released, should we upgrade?
Posted by Ersin Er <er...@gmail.com>.
It's working fine for building 1.5 trunks and integration tests.
On 6/25/07, Emmanuel Lecharny <el...@gmail.com> wrote:
> Hi,
>
> does it work fine ?
>
> If so, let's just switch
>
>
> On 6/25/07, Ersin Er <er...@gmail.com> wrote:
> > http://maven.apache.org/release-notes.html
> >
> > --
> > Ersin Er
> >
> > R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
> > http://www.cs.hacettepe.edu.tr
> >
> > Committer and PMC Member of The Apache Directory Project
> > http://directory.apache.org
> >
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
--
Ersin Er
R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
http://www.cs.hacettepe.edu.tr
Committer and PMC Member of The Apache Directory Project
http://directory.apache.org
Re: [Build] Maven 2.0.7 released, should we upgrade?
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi,
does it work fine ?
If so, let's just switch
On 6/25/07, Ersin Er <er...@gmail.com> wrote:
> http://maven.apache.org/release-notes.html
>
> --
> Ersin Er
>
> R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
> http://www.cs.hacettepe.edu.tr
>
> Committer and PMC Member of The Apache Directory Project
> http://directory.apache.org
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com