org.eclipse.virgo.web.dm from p2?https://www.eclipse.org/forums/index.php/mv/msg/477559/1042946/#msg_1042946
http://download.eclipse.org/virgo/updatesite/3.6.1.RELEASE
or http://download.eclipse.org/gemini/updates/web/2.2.0]]>Mixa Alekseev2013-04-17T04:21:40-00:00Re: org.eclipse.virgo.web.dm from p2?https://www.eclipse.org/forums/index.php/mv/msg/477559/1043448/#msg_1043448
It is not published in a consumable way to a p2 repo at the moment.
However you can find it in Ivy and Maven. As a workaround you can add a regular Maven dependency to it in your build and use the tycho options that considers maven dependencies into the resolution of the target platform.
Here is an example how to congfigure the tycho plugin:

Hope that helps,
Bobby]]>Borislav Kapukaranov2013-04-17T18:09:11-00:00Re: org.eclipse.virgo.web.dm from p2?https://www.eclipse.org/forums/index.php/mv/msg/477559/1043478/#msg_1043478
Even though the bundle in question is available in Maven, its dependencies are not there (those with o.e.v.mirrored groupID).
What tycho does when considering pom dependencies is to first try to resolve following the Maven rules and then merge with the available p2 repos.
So in this case it won't be able to resolve web.dm in the first place in order to include it in the target platform.

Two ways to proceed
- either make all o.e.v.mirror artifacts available in Maven, not only in Ivy (this is covered by bug 386456)
- or publish web.dm and other /repository/* resources in a p2 repo

If you prefer the latter please open a ticket. If not vote for bug 386456.]]>Borislav Kapukaranov2013-04-17T19:08:11-00:00