Dag, you're right of course. I'll take a look and/or log some issues in JIRA. Myrna
On Tue, Jun 10, 2014 at 12:26 PM, Dag H. Wanvik <[email protected]> wrote: > > On 09. juni 2014 19:40, Myrna van Lunteren wrote: > > >So I think at this point I will just accept that we cannot run the lucene > tests with classes. > > But shouldn't the tests themselves just skip tests that can't be run with > classes only? > > Thanks, > Dag > > > > I was planning to look into this, but after svn update to the latest > state and running the LuceneSupportPermsTest by itself with just classes > (and the tools/lucene* jar files) in my classpath, I see failures with the > cause: > Caused by: java.lang.IllegalArgumentException: A SPI class of type > org.apache.lucene.codecs.Codec with name 'Lucene46' does not exist. You > need to add the corresponding JAR file supporting this SPI to your > classpath.The current classpath supports the following names: [] > > > > > Myrna > > > > On Mon, Jun 9, 2014 at 5:11 AM, Rick Hillegas <[email protected]> > wrote: > >> On 6/6/14 1:39 PM, Myrna van Lunteren wrote: >> >>> Hi, >>> >>> I was running the lang._Suite with (sane) classes and ran into errors >>> like this in the LuceneSupportPermsTest methods: >>> 1) >>> test_001_basicNoGrant(org.apache.derbyTesting.functionTests.tests.lang.LuceneSupportPermsTest)java.sql.SQLException: >>> The exception 'java.security.AccessControlException: Access denied >>> (java.lang.RuntimePermission accessDeclaredMembers)' was thrown while >>> evaluating an expression. >>> >>> I know we no longer expect to be able to run the full suite successfully >>> with just classes, but I wonder if it is possible to add this permission? >>> (note: I do have the lucene jars in the CLASSPATH). >>> >>> Thx, >>> Myrna >>> >> Hi Myrna, >> >> This sounds like a reasonable change. >> >> Thanks, >> -Rick >> > > >
