Hi
Matthias, first of, thanks a lot for the pointers. Having a
project to "steal" most of the setup from really makes this job
quite a bit easier. Btw: I spent most of my time figuring out how
to produce a suitable category.xml file. From what I understand,
and I learnt today that I still understand very little ;), this
basically does all the steps that Denis described in his previous
post (creating a p2 repo, etc..)
I got around to playing with the eclipse-signing-maven-plugin
today and I think, I have a working version locally. I'm going to
let Martin review my changes and wait for the answers to my
question below before pushing to the babel repo though.
@Denis, Matthias: it seems that egit copies the repository
directly to the downloads section
(/home/data/httpd/download.eclipse.org/...), correct?
@Denis: you mentioned that the webmasters are not so happy about
this approach. If it is ok with you I would still like to take the
direct route first to test the setup etc and then subsequently
introduce the cron job, once everything is working.
currently, I would use the following two directories:
* temp location for signing:
/home/data/httpd/download-staging.priv/technology/babel
* destination for singed p2 repository:
/home/data/httpd/download.eclipse.org/technology/babel/tools-updates-nightly
If these directories are ok, I will create them on
build.eclipse.org (I just tested, unblocked and used my shell
access ;) ) and then push my changes and test them on the server
with hudson.
Cheers
Stefan
On 28.11.2012 23:21, Matthias Sohn wrote:
2012/11/28 Stefan Strobl <stefan.strobl@xxxxxxxxxxxxxxxxx>
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev