I think that the “sign” script actually does a repack automagically though I’m not 100% sure.
At any rate you wouldn’t run pack200 directly but you should use the Eclipse jarprocessor as wrapper.
http://wiki.eclipse.org/Pack200#Jar_Processor
I haven’t it tested it lately but this should work:
java -jar org.eclipse.equinox.p2.jarprocessor_<version>.jar –pack org.eclipse.tm.repo.zip
The E-Mail is delivered to your committer ID on build.eclipse.org – the shell will display “You’ve got new mail” when done.
You can read it by typing “mail” on your shell.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of David Dykstal
Sent: Monday, February 04, 2013 6:57 PM
To: TM project developer discussions
Subject: Re: [tm-dev] TM committer call this week (signing)
Looks good. I think we'll go with this approach. It appears I already have signing authority. I still have some minor questions.
- pack200 - I assume I want to run a repack on all the jars to be signed prior to submission, correct? I'm not too familiar with this. Can I run pack200 --repack on the whole repo at once?
- how does sign know where to send the completion mail?
-- David Dykstal, Architect - Rational Developer for Power Systems
From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To: TM project developer discussions <tm-dev@xxxxxxxxxxx>,
Date: 02/04/2013 11:29 AM
Subject: Re: [tm-dev] TM committer call this week
Sent by: tm-dev-bounces@xxxxxxxxxxx
Hi Dave,
You can sign your entire repo.zip in one step:
ssh build.eclipse.org
cd /home/data/httpd/download-staging.priv/tools/tm/
cp (your-source)/org.eclipse.tm.repo.zip .
sign org.eclipse.tm.repo.zip mail
[wait for e-mail to arrive that signing is done]
cp org.eclipse.tm.repo.zip (your-target)
I think you’re right that you need to be in the “signers” group (8303) to have permission to do that.
Just type “id” on build.eclipse.org to check. I think only signers can execute the “sign” script.
I think you can file a bug against Community asking to get signer permission if need be.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From:
tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of David Dykstal
Sent: Monday, February 04, 2013 6:06 PM
To: TM project developer discussions
Subject: Re: [tm-dev] TM committer call this week
Martin --
Manually signing might be an option. After doing some more research (and reaching back into my memory) it appears we'd want to run a pack200 on the repository to condition the jars and then submit it for signing. It doesn't sound too hard to do manually, but
I have yet to figure out how much to unzip the repo and the exact commands needed to condition the jars and submit the whole package for signing. Can this be done with one command or would each plugin jar require its own submission?
It appears that one needs special permission to submit jars to the signing machine. I assume you have that. Is there some way to tell if Anna or I have that permission?
-- David Dykstal, Architect - Rational Developer for Power Systems
From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To: TM project developer discussions <tm-dev@xxxxxxxxxxx>,
"Stieber, Uwe" <Uwe.Stieber@xxxxxxxxxxxxx>,
Date: 02/04/2013 10:28 AM
Subject: Re: [tm-dev] TM committer call this week
Sent by: tm-dev-bounces@xxxxxxxxxxx
Hi Dave,
I’m afraid I wouldn’t be of much help regarding the jar signing … since I’m no Tycho expert.
Uwe, you’re also a TM committer, could you perhaps help Anna based on your experience with TCF ?
If nothing helps on the automation side of things, then I could offer manually signing the contribution, or helping you do that.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From:
tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of David Dykstal
Sent: Monday, February 04, 2013 3:15 PM
To: TM project developer discussions
Subject: Re: [tm-dev] TM committer call this week
Martin --
That should be OK.
Our major issue right now is jar signing. We cannot release SR2 without it. Any ideas, pointers, etc. would be helpful. I'm pretty sure it has to be fixed in the top-level pom using some sort of Tycho magic, but that's as far as I've gotten so far.
-- David Dykstal, Architect - Rational Developer for Power Systems
From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To: TM project developer discussions <tm-dev@xxxxxxxxxxx>,
Date: 02/04/2013 04:15 AM
Subject: Re: [tm-dev] TM committer call this week
Sent by: tm-dev-bounces@xxxxxxxxxxx
Hi Dave,
Thanks for the reminder but I’m afraid I can’t make it tomorrow – my calendar is packed.
I could probably join a couple hours later, but it might be a better idea for you guys to meet without me – I’ll read the notes and follow up offline if there’s anything outstanding.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From:
tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of David Dykstal
Sent: Sunday, February 03, 2013 9:05 PM
To: tm-dev@xxxxxxxxxxx
Subject: [tm-dev] TM committer call this week
This is just a quick reminder that we have our TM committer call this Tuesday at 1700 UTC (1200 Toronto). I will post the agenda by Monday night (2300 GMT-6) at
http://wiki.eclipse.org/TM/Meetings/5-Feb-2013. Post here
if you have items that should be added.
-- David Dykstal, Architect - Rational Developer for Power Systems_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tm-dev_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tm-dev_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tm-dev
