Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] Re: [bpmn-dev] Promote build BPMN 1.0.2

Nick, this is a maintenance build of an earlier version of BPMN for Ganymede, we have made progress for Galileo, but we haven't ported it.

Thanks,

Antoine

On Wed, Apr 29, 2009 at 08:51, Nick Boldt <nickboldt@xxxxxxxxx> wrote:
In a p2 repo you need only these bits:

artifacts.xml or artifacts.jar
content.xml or content.jar
plugins/*.jar.pack.gz
features/*.jar

site.xml is only required if you expect anyone to unpack the zip and use it with Eclipse3.3 or earlier, or a p2-disabled version of Eclipse 3.4+. It is needed, however, to generate categori(es) for your metadata (artifacts.*, content.*).

"rebuild it by hand" sounds like an error-prone and time-consuming step. Have you met Athena [1]? She'll do it for you if you use build.steps=buildUpdate (plus other steps if desired). She'll even generate the site.xml for you from the features she just built before using that to gen the p2 metadata.

[1]http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Eclipse

N


Oisin Hurley wrote:
That zip contains a feature.jar, but no p2 metadata or site.xml. To install
it I therefore have to unpack the zip, unpack the feature.jar, and dump
everything in dropins/ ... right?

Could the zip include p2 metadata so it's easier to use?

I'm sure it could! And it will in a couple of minutes once I just rebuild
it by hand.

It still has jars + pack.gz files in it - are the jars redundant now,
can I just leave them out?  Is there any point in including the
site.xml and the digest now with the p2 metadata in place? Small
questions indeed, but just checking to see if there any places to
cut fat.

 cheers
 --oh

--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
Release Engineer :: Eclipse Modeling & Dash Athena


Back to the top