Are you both seeing this error?
If not, it may be that the working directory is corrupt. The Ldap server
tries to write to {java.io.tmpdir}/apacheds-work. Ideally it should
delete the contents of this every time it starts up, or the maven script
would, but it doesn't at the moment.
Try removing that directory and see if it works.
I'll try rebuilding on a couple of different machines too.
Carlos Sanchez wrote:
> I suggest to Luke to wipe out his local repo and try.
> I think it's best to have the initialization in the constructor or
> errors wil lbe hard to debug.
>
>
> On 5/27/06, Ben Alex <[EMAIL PROTECTED]> wrote:
>> Luke Taylor wrote:
>>> I'm not seeing any problems with the latest code... I just rebuilt the
>>> web site and all the tests seems to be passing.
>>>
>>> There's quite a serious overhead in starting up the Ldap server which is
>>> why I made it a static field. Maven 1 seems to reload the class each
>>> time it runs a test so it doesn't an you ke much difference but it's a lot
>>> faster running in IntelliJ or Maven 2.
>>>
>>> Moving it to the constructor would probably be OK, but putting it in the
>>> setUp would slow things down a lot.
>>>
>> Hi Luke
>>
>> Whether I use Maven 1, Maven 2 or Eclipse, running the unit tests is
>> always reporting:
>>
>> jdbm.helper.WrappedRuntimeException:
>> org.apache.ldap.server.partition.impl.btree.jdbm.JdbmMasterTable$1
>> at jdbm.helper.DefaultSerializer.deserialize(DefaultSerializer.java:99) etc
>>
>> Whilst researching this, I noticed someone else on the forum reported
>> exactly the same exception.
>>
>> Given the public site is building fine with Maven 1 - including the LDAP
>> tests
>> (http://acegisecurity.org/multiproject/acegi-security/junit-report.html#org_acegisecurity_providers_ldap)
>> - I am wondering if there is a version issue with one of the Apache
>> Directory JARs at http://acegisecurity.sourceforge.net/maven. I've tried
>> deleting all of my local JARs so they refresh from the public repo, but
>> it still fails. By some chance are you running a different version of
>> the JARs, even though their filenames suggest you are not (perhaps try
>> an md5sum on your local JARs and compare them with an md5sum executed on
>> the SourceForge shell server)?
>>
>> We cannot release 1.0.0 whilst this issue remains. Also, I am also going
>> to Brisbane this afternoon until Thursday night, and on Friday morning I
>> am going to Europe. So we really need this resolved ASAP if there is to
>> be any chance at all of getting 1.0.0 out before I return to Australia
>> in July.
>>
>> Cheers
>> Ben
>>
>>
>> _______________________________________________
>> Home: http://acegisecurity.org
>> Acegisecurity-developer mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>>
>
>
--
Luke Taylor. Monkey Machine Ltd.
PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
_______________________________________________
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
