Le 14/11/14 14:49, Shawn McKinney a écrit :
> On 11/14/2014 03:50 AM, Emmanuel Lécharny wrote:
>> I have updated the pom for those new versions.
>>
>> When I run the test with mvn clean install, I get many errors, most
>> certainly due to the missing configuration file. At some point, we
>> should probably create such a configuration file, instead of generating
>> it with ant.
> What errors do you get for which test(s)? To run for a specific test try:
>
> $M2_HOME/bin/mvn -Dtest=FortressJUnitTest test
This is what I get :
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.29 sec
<<< FAILURE! - in org.apache.directory.fortress.core.rbac.FortressJUnitTest
initializationError(org.apache.directory.fortress.core.rbac.FortressJUnitTest)
Time elapsed: 0.006 sec <<< ERROR!
java.lang.ExceptionInInitializerError: null
at
org.apache.directory.fortress.core.cfg.Config.<clinit>(Config.java:70)
at
org.apache.directory.fortress.core.util.attr.VUtil.<clinit>(VUtil.java:49)
at
org.apache.directory.fortress.core.util.LogUtil.getContext(LogUtil.java:75)
at
org.apache.directory.fortress.core.util.LogUtil.logIt(LogUtil.java:46)
at
org.apache.directory.fortress.core.rbac.ReviewMgrImplTest.teardownRequired(ReviewMgrImplTest.java:339)
at
org.apache.directory.fortress.core.rbac.FortressJUnitTest.getFirstRun(FortressJUnitTest.java:70)
at
org.apache.directory.fortress.core.rbac.FortressJUnitTest.<clinit>(FortressJUnitTest.java:65)
Results :
Tests in error:
FortressJUnitTest.<clinit>:65->getFirstRun:70 » ExceptionInInitializer
