<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/05/2012 08:08 PM, Rob Cernich wrote:
<blockquote
cite="mid:f069ad02-d044-4b7f-87cf-f13f9206070e@zmail13.collab.prod.int.phx2.redhat.com"
type="cite">
<pre wrap="">Hey all,</pre>
</blockquote>
Hi,<br>
<br>
<blockquote
cite="mid:f069ad02-d044-4b7f-87cf-f13f9206070e@zmail13.collab.prod.int.phx2.redhat.com"
type="cite">
<pre wrap="">Since v. 5.4 is not in the nightly SOA repo, how would one go about setting up the SY tooling project to reference the Drools tools 5.4 snapshot builds?</pre>
</blockquote>
Before, you were part of the same Reactor (ie Maven build context)
as your dependencies, then your deps where resolved in this reactor.
Now you are "alone", so you'll have to provide a way to resolve this
dependencies. If you are running in the same M2_REPO, then Maven can
resolve your deps to the content of this M2_REPO. However, it is not
that clean, so if you choose this solution, you'll probably complain
within a few weeks/months ;) <br>
<br>
The real good alternative would be for you to add a dependency to
the p2 repository that you want to use in order to resolve SOA
stuff. You need Drools to provide you an update-site/p2 repository
that contains what you want to build, and then add this repository
to your pom.xml. When it is done, Maven will use it to resolve the
new stuff.<br>
This is the same principle as "standard" Maven, except that instead
of Maven repositories, you use p2 repositories.<br>
<br>
HTH<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>