Re: [nebula-dev] NatTable build help

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi,

On 09/12/2012 06:03 PM, Edwin Park wrote:

1. Sign jars with the Eclipse cert

We directly sign the generated update-site. This is done using the eclipse-signing-maven-plugin, See http://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tree/releng/org.eclipse.nebula.updatesite/pom.xml fpr an example of usage. After you invoked this plugin, the signed repo is available in target/checksumFix folder.
You'll notice we use a profile, since this plugin only works on build.eclipse.org.

Another plugin is available, but I never tried it.

2. Create p2 repository

See same pom: it's an eclipse-repository packaging type, and it uses a category.xml to define the content of the repository. Category.xml has same syntax as site.xml, so you can simply rename a site.xml you like into category.xml

Also, when we release our binaries on build.eclipse.org I was thinking of putting them under /shared/technology/nebula/nattable. Let me know if that's ok with you guys.

Build.eclipse.org is not recommanded for publishing stuff. You should use download.eclipse.org instead, that you can access from most Ecipse machines through folder  /home/data/httpd/download.eclipse.org.

See the configuration of Jenkins job for exemple of build invocation and publishing https://hudson.eclipse.org/hudson/job/nebula.nebula/configure

HTH

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets