Hi Ole Am 08.08.2013 um 18:13 schrieb Ole Ersoy:
> Hi Felix, > > Sounds great. Please let me know if there's anything I can do to help. Thanks for the offer. This failure has been fixed by us updating the Event bundle tests to the latest Jackrabbit Server bundle (actually the Event bundle is currently under vote). So the build should now run again and all tests should pass. Regards Felix > > Thanks, > - Ole > > > On 08/08/2013 01:11 AM, Felix Meschberger wrote: >> Hi >> >> Your are hitting a "temporary" issue: The repository configured in the the >> integration test of the Sling Eventing bundle is not really functional. We >> are currently releasing the affected bundle and later today, I will >> configure it in the Sling Eventing bundle such that the tests should run and >> pass again. >> >> In the meantime, I suggest you build with the tests disabled. Sorry for the >> inconvenience. >> >> See also this thread on dev@: >> http://sling.markmail.org/thread/7dcxlni7tulovxs2 >> >> Regards >> Felix >> >> >> Am 08.08.2013 um 04:29 schrieb Ole Ersoy: >> >>> Hi, >>> >>> I'm trying to run the build. >>> >>> First I try this: >>> >>> export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=512m" >>> mvn -s /dev/null clean install >>> >>> And I get this: >>> >>> [ERROR] Error executing Maven. >>> [ERROR] The specified user settings file does not exist: /dev/null >>> >>> Then I tried running it without the /dev/null part and it hangs while >>> printing the below over and over. >>> >>> 07.08.2013 21:17:57.526 *ERROR* [Repository Pinger] >>> org.apache.sling.jcr.jackrabbit.server acquireRepository: Repository >>> problem starting repository from >>> file:/home/ole/Experiment/sling/source/sling/bundles/extensions/event/jackrabbit/repository.xml >>> in jackrabbit (javax.jcr.RepositoryException: The repository home >>> /home/ole/Experiment/sling/source/sling/bundles/extensions/event/jackrabbit >>> appears to be in use since the file named .lock is already locked by the >>> current process.) javax.jcr.RepositoryException: The repository home >>> /home/ole/Experiment/sling/source/sling/bundles/extensions/event/jackrabbit >>> appears to be in use since the file named .lock is already locked by the >>> current process. >>> at >>> org.apache.jackrabbit.core.util.RepositoryLock.tryLock(RepositoryLock.java:159) >>> at >>> org.apache.jackrabbit.core.util.RepositoryLock.acquire(RepositoryLock.java:138) >>> at >>> org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:302) >>> at >>> org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:673) >>> at >>> org.apache.sling.jcr.jackrabbit.server.impl.SlingServerRepository.acquireRepository(SlingServerRepository.java:141) >>> at >>> org.apache.sling.jcr.base.AbstractSlingRepository.startRepository(AbstractSlingRepository.java:746) >>> at >>> org.apache.sling.jcr.base.AbstractSlingRepository.run(AbstractSlingRepository.java:876) >>> at java.lang.Thread.run(Thread.java:724) >>> >>> Thoughts? >>> >>> Thanks, >>> - Ole >>> >>> P.S. Here's my mvn and java version info just in case: >>> Apache Maven 3.0.4 >>> Maven home: /usr/share/maven >>> Java version: 1.7.0_25, vendor: Oracle Corporation >>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre >>> Default locale: en_US, platform encoding: UTF-8 >>> OS name: "linux", version: "3.8.0-27-generic", arch: "amd64", family: "unix" >> >>
