Do we have commit privs for that?<br><br>Ralph<br><br><div class="gmail_quote">On Mon, Nov 17, 2008 at 11:24 AM, Ceki Gulcu <span dir="ltr"><listid@qos.ch></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Hello Ralph, Thorbjørn,<br>
<br>
How about using the 'integration' module? It is designed for testing after all<br>
the SLF4J jars have been already produced.<br>
<div class="Ih2E3d"><br>
ralph.goers @<a href="http://dslextreme.com" target="_blank">dslextreme.com</a> wrote:<br>
> See<br>
> <a href="http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html" target="_blank">http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html</a>.<br>
> Maven has a process-test-classes phase after test-compile and before<br>
> test. You want to add a jar plugin that runs in that phase and have it<br>
> create the jar you need for testing in the target directory.<br>
><br>
> A second alternative is to run your tests during the integration-test<br>
> phase. It is possible, but tricky, to configure the surefire plugin to<br>
> run in both the test and integration-test phases by disabling tests on<br>
> the plugin and then configuring executions in the plugin where the tests<br>
> are enabled. If you'd like to try this and have no idea what I am<br>
> talking about let me know and I will post an example.<br>
><br>
> On Mon, Nov 17, 2008 at 10:12 AM, Thorbjørn Ravn Andersen<br>
</div><div class="Ih2E3d">> <<a href="mailto:ravn@runjva.com">ravn@runjva.com</a> <mailto:<a href="mailto:ravn@runjva.com">ravn@runjva.com</a>>> wrote:<br>
><br>
> Ceki Gulcu skrev:<br>
> > Optional means that the artifact is not exported transitively. It<br>
> should not<br>
> > affect the compile or test class paths.<br>
> ><br>
> Ok, then let's take the "how to test"-debate now :)<br>
><br>
> The problem is that in order to do the testing the ext.jar must be<br>
> built and used, but as far as I can see the test phase happens<br>
> before the installation phase. Hence I tried moving the testing to<br>
> another maven project but then it needs to know which Javassist<br>
> library to use to do this properly.<br>
><br>
> Right now I am including the relative path to the library retrieved<br>
> by maven in the built jar, but this is rather sneaky I think.<br>
><br>
> Suggestions?<br>
><br>
> --<br>
> Thorbjørn Ravn Andersen "...plus... Tubular Bells!"<br>
><br>
> _______________________________________________<br>
> dev mailing list<br>
</div>> <a href="mailto:dev@slf4j.org">dev@slf4j.org</a> <mailto:<a href="mailto:dev@slf4j.org">dev@slf4j.org</a>><br>
<div class="Ih2E3d">> <a href="http://www.slf4j.org/mailman/listinfo/dev" target="_blank">http://www.slf4j.org/mailman/listinfo/dev</a><br>
><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div class="Ih2E3d">><br>
> _______________________________________________<br>
> dev mailing list<br>
> <a href="mailto:dev@slf4j.org">dev@slf4j.org</a><br>
> <a href="http://www.slf4j.org/mailman/listinfo/dev" target="_blank">http://www.slf4j.org/mailman/listinfo/dev</a><br>
<br>
</div><div class="Ih2E3d">--<br>
Ceki Gülcü<br>
Logback: The reliable, generic, fast and flexible logging framework for Java.<br>
<a href="http://logback.qos.ch" target="_blank">http://logback.qos.ch</a><br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">dev mailing list<br>
<a href="mailto:dev@slf4j.org">dev@slf4j.org</a><br>
<a href="http://www.slf4j.org/mailman/listinfo/dev" target="_blank">http://www.slf4j.org/mailman/listinfo/dev</a><br>
</div></div></blockquote></div><br>