You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, Wisdom relies on the maven failsafe plugin to run integration test. So it just needs some configuration in the failsafe plugin.
I'm going to update the default pom.xml file to set the working directory to target/wisdom. However, be aware that you IDE, will require manual tweaks.
your application should not base its 'file' lookup on the working directory. This si really error prone
changing the working directory of failsafe impact a lot of things such as the bundle packaging strategy as files are not found anymore (BND use relative paths)
So, I need to think more about this.
For now, there is a simple work around. The ApplicationConfiguration service has a getBaseDirectory method retrieving the Wisdom root directory.
However, what is strange is that if you look at the code of the CndImportOperation and especially at getInputStreamForFile and IoUtil.getResourceAsStream you will note that ModeShape do rely on the classloader to load the ressource and not on a working directory.
That's why I suspected an issue in Wisdom failsafe configuration. By the way adding manullay in the pom ${basedir}/target/wisdom to the failsafe classpath does fix the issue.
Anyway, it seems that updating the failsafe base directory is a bit more complicated than expected :)
So I guess that we will go with the failsafe workaround for the moment.
This leads to some strange ressource loading issues like Modeshape does not load cnd files from conf directory when running tests #12 in wisdom-jcr
The application should be executed in the same directory both with wisdom:run and with surefire.
The text was updated successfully, but these errors were encountered: