<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="moz-cite-prefix">On 10/23/2013 04:06 PM, Rob Cernich
wrote:<br></div><blockquote cite="mid:509919367.12038306.1382537168442.JavaMail.root@redhat.com">
Don't you have to jump through hoops in the pom to get nexus
dependencies incorporated into a tycho project? Is the use case
that specific Locus plugins will be added to a target platform,
resolved through a normal dependency (as opposed to using a p2
repo in the pom)? Sorry in advance for my ignorance here (seems
like I might learn something).
</blockquote>
No, the output of Locus is a valid p2 repo to consume in target
definitions. No hack necessary (it's the whole purpose of Locus).</blockquote><div>Thanks Mickael, that was my understanding. What was all that stuff Max was saying about deploying to nexus, not having to publish, etc.? What was I missing there?<br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools" target="_blank">JBoss,
by Red Hat</a><br><a href="http://mickaelistria.wordpress.com" target="_blank">My blog</a> - <a href="http://twitter.com/mickaelistria" target="_blank">My Tweets</a><br data-mce-bogus="1"></div><br>_______________________________________________<br>jbosstools-dev mailing list<br>jbosstools-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev</blockquote><div><br></div></div></body></html>