[slf4j-dev] New Class

[ralph.goers @dslextreme.com]

See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html.
Maven has a process-test-classes phase after test-compile and before test.
You want to add a jar plugin that runs in that phase and have it create the
jar you need for testing in the target directory.

A second alternative is to run your tests during the integration-test phase.
It is possible, but tricky, to configure the surefire plugin to run in both
the test and integration-test phases by disabling tests on the plugin and
then configuring executions in the plugin where the tests are enabled.  If
you'd like to try this and have no idea what I am talking about let me know
and I will post an example.

On Mon, Nov 17, 2008 at 10:12 AM, Thorbjørn Ravn Andersen
<ravn at runjva.com>wrote:

> Ceki Gulcu skrev:
> > Optional means that the artifact is not exported transitively. It should
> not
> > affect the compile or test class paths.
> >
> Ok, then let's take the "how to test"-debate now :)
>
> The problem is that in order to do the testing the ext.jar must be built
> and used, but as far as I can see the test phase happens before the
> installation phase.  Hence I tried moving the testing to another maven
> project but then it needs to know which Javassist library to use to do this
> properly.
>
> Right now I am including the relative path to the library retrieved by
> maven in the built jar, but this is rather sneaky I think.
>
> Suggestions?
>
> --
>  Thorbjørn Ravn Andersen  "...plus... Tubular Bells!"
>
> _______________________________________________
> dev mailing list
> dev at slf4j.org
> http://www.slf4j.org/mailman/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://qos.ch/pipermail/slf4j-dev/attachments/20081117/dba930ad/attachment.htm>