[jbosstools-dev] How do I compile against org.jboss.tools.tests?

[Max Rydahl Andersen]

On Sat, Oct 05, 2013 at 08:23:14AM -0400, Ian Tewksbury wrote:
>Max,
>
>Once I imported the org.jboss.tools.tests plugin into my workspace the
>windup-eclipse-plugin project would compile via mvn clean verify.
>
>I actually found this very interesting. I had expected the import to work
>for making Eclipse happy, 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.

That does not make sense. mvn and eclipse dependency resolution is completely
seperate so this should not work ;)

>It would be a good experiment to have someone else download the windup
>plugin and try a mvn clean verify and see what happens.

I just git cloned and ran mvn clean verify and I got this:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] windup.all ........................................ SUCCESS [0.989s]
[INFO] windup.plugins .................................... SUCCESS [0.011s]
[INFO] org.jboss.tools.windup.core ....................... FAILURE [23.230s]
[INFO] windup.features ................................... SKIPPED
[INFO] org.jboss.tools.windup.feature .................... SKIPPED
[INFO] windup.tests ...................................... SKIPPED
[INFO] org.jboss.tools.windup.core.test .................. SKIPPED
[INFO] site .............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:01.472s
[INFO] Finished at: Mon Oct 07 10:27:42 CEST 2013
[INFO] Final Memory: 45M/648M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project org.jboss.tools.windup.core: Could not resolve dependencies for project org.jboss.tools.windup.plugins:org.jboss.tools.windup.core:eclipse-plugin:1.0.0-SNAPSHOT: The following artifacts could not be resolved: org.jboss.windup:windup-engine:jar:0.7.0, org.jboss.windup:windup-metadata:jar:0.7.0, org.jboss.windup:windup-reporting:jar:0.7.0, org.jboss.windup:windup-rules:jar:0.7.0: Could not find artifact org.jboss.windup:windup-engine:jar:0.7.0 in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :org.jboss.tools.windup.core
mvn clean verify  30.45s user 2.27s system 50% cpu 1:05.11 total

My guess is you depend on a windup release that is not yet available ?
(or I got some screwed up settings.xml ;)

/max

>Blue Skies,
>
>~Ian
>
>-----Original Message-----
>From: jbosstools-dev-bounces at lists.jboss.org
>[mailto:jbosstools-dev-bounces at lists.jboss.org] On Behalf Of Max Rydahl
>Andersen
>Sent: Saturday, October 05, 2013 5:07 AM
>To: Mickael Istria
>Cc: jbosstools-dev at lists.jboss.org
>Subject: Re: [jbosstools-dev] How do I compile against
>org.jboss.tools.tests?
>
>On Fri, Oct 04, 2013 at 05:37:43PM +0200, Mickael Istria wrote:
>>On 10/04/2013 05:36 PM, Nick Boldt wrote:
>>>Note that
>>>http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
>>>4.1.kepler/ is a bit out of date - hasn't been updated since May 2013.
>>Thanks Nick for correcting this wrong link ;) Since Ian chose to import
>>project in workspace, my bad suggestion shouldn't have created too much
>>trouble.
>
>he still need to be able to build with maven so we need something more
>stable than "import into workspace" :)
>
>/max
>
>>--
>>Mickael Istria
>>Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My
>>blog <http://mickaelistria.wordpress.com> - My Tweets
>><http://twitter.com/mickaelistria>
>
>>_______________________________________________
>>jbosstools-dev mailing list
>>jbosstools-dev at lists.jboss.org
>>https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>_______________________________________________
>jbosstools-dev mailing list
>jbosstools-dev at lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/jbosstools-dev