<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 10/05/2013 02:23 PM, Ian Tewksbury
wrote:<br>
</div>
<blockquote cite="mid:04f734cf.000029b4.0000001c@RHCR9L4HN9"
type="cite">
<pre wrap="">Once I imported the org.jboss.tools.tests plugin into my workspace the
windup-eclipse-plugin project would compile via mvn clean verify.
[...]
I had not expected it to make the maven compile
issues happy. I was also surprised that the maven build was not working in
the first place. It never had issues picking up the jbosstools parent, but
for some reason it was having issues picking up the org.jboss.tools.test
plugin. But then as soon as I imported the project into my workspace and
then did a clean verify on the windup-eclipse-plugin its complaining about
not being able to find the test classes went away.
</pre>
</blockquote>
That's probably not exactly how it happens ;)<br>
Maven is not aware of you workspace, so the cause of this happiness
is something else. However, it is not possible to figure out the
cause without knowing the error you got ealier.<br>
<br>
<blockquote cite="mid:04f734cf.000029b4.0000001c@RHCR9L4HN9"
type="cite">
<pre wrap="">It would be a good experiment to have someone else download the windup
plugin and try a mvn clean verify and see what happens.</pre>
</blockquote>
Better: create a job on Jenkins CI, so you'll know what happens
anytime you push a commit.<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>