Return-Path: X-Original-To: apmail-uima-dev-archive@www.apache.org Delivered-To: apmail-uima-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8E26DDC39 for ; Fri, 5 Oct 2012 21:34:03 +0000 (UTC) Received: (qmail 84897 invoked by uid 500); 5 Oct 2012 21:34:03 -0000 Delivered-To: apmail-uima-dev-archive@uima.apache.org Received: (qmail 84845 invoked by uid 500); 5 Oct 2012 21:34:03 -0000 Mailing-List: contact dev-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@uima.apache.org Delivered-To: mailing list dev@uima.apache.org Received: (qmail 84729 invoked by uid 99); 5 Oct 2012 21:34:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 21:34:02 +0000 Date: Fri, 5 Oct 2012 21:34:02 +0000 (UTC) From: "Steven Bethard (JIRA)" To: dev@uima.apache.org Message-ID: <1595909356.3028.1349472842995.JavaMail.jiratomcat@arcas> In-Reply-To: <2003927479.851.1349371670739.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (UIMA-2475) eclipse p2 update site instead of old-style update site MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470685#comment-13470685 ] Steven Bethard commented on UIMA-2475: -------------------------------------- I've never done this, but according to the wiki: http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Releng#Update_sites You should run the the p2 update site publisher (http://wiki.eclipse.org/Equinox/p2/Publisher#UpdateSite_Publisher_Application) on the old site, which I guess looks like this: java -jar /plugins/org.eclipse.equinox.launcher_*.jar -application org.eclipse.equinox.p2.publisher.UpdateSitePublisher -metadataRepository file://repository -artifactRepository file://repository -source / -configs gtk.linux.x86 -compress -publishArtifacts If it worked right, I think it should add a content.xml and artifacts.xml file to your update site. I'm not 100% sure, but the wiki makes it look like that might be all you need to do. > eclipse p2 update site instead of old-style update site > ------------------------------------------------------- > > Key: UIMA-2475 > URL: https://issues.apache.org/jira/browse/UIMA-2475 > Project: UIMA > Issue Type: Bug > Components: Eclipse plugins > Reporter: Steven Bethard > > The UIMA Eclipse update site (www.apache.org/dist/uima/eclipse-update-site) is an Eclipse 3.3 (or older) update site. Since Eclipse 3.4, the recommended update site layout is p2: > http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Releng#Why_should_I_make_changes_to_adopt_p2.3F > I've been bitten by this update site issue because old-style update sites make it impossible to resolve build-time dependencies when building Eclipse plugins: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380438#c3 > Could the UIMA update site be modernized to the p2 layout? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira