Hi Marco,
On Fri, Nov 11, 2011 at 4:53 PM, Marco Glur <[email protected]> wrote:
>
>
> Currently I ran into problems with the tests using the magnolia core
> test-jar, referencing it as test-dependency works for mocking in the IDE.
> As
> soon running the tests from the Maven command-line, it doesn't find any
> module descriptors and fails. Most likely some class-loader issues while
> searching the /META-INF/magnolia/ folders in the referenced jars.
>
This can usually be solved by setting the "useManifestOnlyJar" surefire
option:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<useManifestOnlyJar>false</useManifestOnlyJar>
</configuration>
</plugin>
Maven uses by default a single autogenerated jar which references all the
real jars in its manifest, as a workaroud to the "command line too long"
problem you may encounter in Windows when your classpath is too long. You
may turn off such behavior with the option above, and that will make
Magnolia classpath discovery working.
HTH
fabrizio
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
