<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/05/2012 10:04 AM, Max Rydahl
Andersen wrote:<br>
</div>
<blockquote
cite="mid:1A244E4E-C685-4887-A177-5C30F67F6DD4@redhat.com"
type="cite">
<pre wrap="">
On 05 Sep 2012, at 04:31, Nick Boldt <a class="moz-txt-link-rfc2396E" href="mailto:nboldt@redhat.com"><nboldt@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So... if you wanted to nest some test plugins for verifying content on the sites, I might suggest site/tests/ as a reasonable place to start.
</pre>
</blockquote>
<pre wrap="">
well site it self is a eclipse-update-site packaging so putting tests subdirs under it is not really possible.
I wonder if I could just add a basic java unit test to this one....i'll try that.
</pre>
</blockquote>
Eclipse-update-site lifecycle mapping does not contain any
compilation phase (see
<a class="moz-txt-link-freetext" href="http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-maven-plugin/src/main/resources/META-INF/plexus/components.xml">http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-maven-plugin/src/main/resources/META-INF/plexus/components.xml</a>
), so you'll need to explicitly invoke maven-compiler-plugin...<br>
Something that may work better:<br>
1. Write your test-case in the tests/ module<br>
2. Invoke surefire in the site pom.xml (in an integration-test step)
and reference this test-case in surefire configuration<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>