| Re: [tycho-user] Consume old update sites as repositories |
or, use the publish-features-and-bundles goal of tycho-p2-extras-plugin [1] Jan [1] http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-p2-extras-plugin/src/test/resources/publisher/testProject/pom.xml --- From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria Sent: Freitag, 11. Januar 2013 12:42 To: tycho-user@xxxxxxxxxxx Subject: Re: [tycho-user] Consume old update sites as repositories On 01/11/2013 12:34 PM, Christian.Pontesegger@xxxxxxxxxxxx wrote: Hi, Hi, typically I add p2 repositories to my poms like this: <repository> <id>Juno</id> <layout>p2</layout> <url>http://download.eclipse.org/releases/juno</url> </repository> Works like a charm. Now I need to add an old-style update site. Is this supported? Which layout type would I have to use? Non-p2 repositories are not supported since they do not contain metadata for dependency resolution. You should think about mirroring the old update-site as a p2 repository, by either: * Re-creating a p2 repo using PDE (redefine a category.xml containing the content of your old update-site and export it. It will add p2 metadata), or * using an Ant script to invoke p2.mirror and p2.publish.featuresAndBundles tasks: http://download.jboss.org/jbosstools/updates/requirements/findbugs/build.xml HTH -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets