[jbosstools-dev] How to setup an eclipse update site for Fuse Eclipse tooling

[Nick Boldt]

Using the publish.sh [1] script is recommended because you'll be using 
the same publish process, publish to the same location, and generate the 
same build-time metadata as the other projects.

There's also promote.sh [2], which you can use to then copy from 
builds/staging/<JOB_NAME> to some other location, and we have a generic 
Jenkins job [3] you can configure to do the promote very easily. (You 
can also clone the job and set different default parameters if you prefer.)

[1] 
https://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/publish.sh
[2] 
https://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/promote.sh
[3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/

We also have a standard convention for generating an index.html page for 
your unpacked update site, which you can fine-tune to use your own 
banner image and other descriptive text.

Some examples of how to set that up in your site's pom.xml:

https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/webtools-site/pom.xml

https://github.com/ModeShape/modeshape-tools/blob/master/site (see 
pom.xml and siteTemplateFolder/index.html)

https://github.com/droolsjbpm/droolsjbpm-tools/tree/master/drools-eclipse/org.drools.updatesite 
(see pom.xml and siteTemplateFolder/index.html)


On 05/31/2013 05:53 AM, Mickael Istria wrote:
> On 05/31/2013 11:35 AM, Lars Heinemann wrote:
>> --> I am currently using eclipse-repository packaging type but what I
>> get by default is org.fusesource.ide.updatesite-7.2.0-SNAPSHOT.zip
>> which would correspond to <artifactId>-<version>.zip.
>> Any idea why I am getting that?
>
> Actually, that's the default behaviour of Tycho and I was wrong about
> repository.zip (it's probably an older convention I had in mind). I
> don't think the zip name is a problem if you publish with a simple scp
> or rsync. By the way, the repository/ folder does contain the same stuff
> as the zip. It's easier to directly us it in order to publish, you can
> save an "unzip" step.
>
>> --> I just wanted to do it in a way other projects do it. But if you
>> say it is not needed then I am fine with that.
> Those scripts tend to solve more problems than necessary, just KISS for
> the beginning, and come to share you future issue to see whether we can
> work on a general way of publishing stuff.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com