When building your stuff, you can use the profiles in our parent pom 
to enable repositories from which to find those plugins.
Or, if you're rolling your own parent pom, add one of these repositories
(p2 update sites) to your pom:
Bleeding edge (up to the minute):
Last good aggregation of the bleeding edge (a few hours ago):
Bleeding edge of the stable branch (latest milestone, could be 6-8 weeks
old or up to the minute):
Last good aggregation of the latest milestone (again, 6-8 weeks old or a
few hours old):
If you don't want sites that update themselves unexpectedly (ie., you
want a release site rather than a CI / SNAPSHOT site), you could look to
this site for your upstream (changes every 6-8 weeks when a new
milestone is released):
On 02/03/2012 11:36 AM, Rob Cernich wrote:
Thanks for the response. Plugins like: org.jboss.tools.test,
Imported test plugins from downstream projects contain errors because of these missing
dependencies. The workaround is to either ignore the errors or import the upstream test
----- Original Message -----
> Test plugins? You mean org.eclipse? org.jboss? swtbot?
> Tell me what you need, I'll tell you where it can be found.
> (Chances are you can find it here:
> On 02/02/2012 04:58 PM, Max Rydahl Andersen wrote:
>> On Feb 1, 2012, at 20:31, Rob Cernich wrote:
>>> Hey all,
>>> I'm configuring a target platform for local development and was
>>> wondering if there were any "sites" that provided test plugins?
>>> (Short of downloading the zips and using those; or my hacky
>>> solution which points to the zips on the download site and which
>>> I wouldn't recommend.)
>> Question for Nick where those end up.
>> I wish PDE wouldn't fail on our target platform - but it always
>> seem to do that.
>> jbosstools-dev mailing list
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools& Dev Studio
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio