[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Problem with Eclipse (3.4) P2 Update Manager

You can accomplish this by adding a reference in your site that refers to the site containing EMF. Your content.xml file would have something like this:

  <references size='2'>
    <repository url='' type='0' options='1'/>
    <repository url='' type='1' options='1'/>

This will add the Ganymede repository (both metadata (type='0') and artifacts (type='1')) as references from your repository. Those repositories will then be used when resolving your plugins and dependencies will be installed from those additional sites as required.


Manas Dadarkar <manasd@xxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx

04/13/2009 10:32 AM

Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

[p2-dev] Problem with Eclipse (3.4) P2 Update Manager

    I had a question regarding the Eclipse P2 Update Manager. I have a set of plugins that have a dependency on EMF. These plugins need to be deployed on an Eclipse environment provided by a third party. My update site doesn't want to host any EMF plugins since they are hosted on the
eclipse.org site. The third party Eclipse environment doesn't have the Ganymede (3.4) update site registered in its Update Manager so when that Eclipse environment tries to install my plugins, the installation fails with the error that the required dependency on EMF was not satisfied.
    The third party does not want to change their Eclipse environment. Can someone provide me with tips on how I can resolve this issue? Any help would be much appreciated

Thanks in advance.



p2-dev mailing list