+1 There is currently provisional API in the org.eclipse.osgi which is currently used by update to check the certificate trust and to verify the content of signed bundles. I assume the jar processor API can use an IProcessStep to which uses the API from the framework to perform this type of check? Or would verifying the signed content continue to be a separate step as it is today in update?
Tom
Andrew Niefer
<[EMAIL PROTECTED]
om> To
Sent by: Equinox development mailing list
equinox-dev-bounc <equinox-dev@eclipse.org>
[EMAIL PROTECTED] cc
Subject
09/10/2007 10:29 Re: [equinox-dev] [vote] graduating
AM the new jar processor bundle
Please respond to
Equinox
development
mailing list
<[EMAIL PROTECTED]
pse.org>
+1
As for doing it now, is there any benefit to waiting?
There is some amount of work that will depend on this change. Both
update.core and pde.build will need to be updated after this change. As
well, the p2.jarprocessor is considered HEAD for bug fixes (there is at
least https://bugs.eclipse.org/bugs/show_bug.cgi?id=190064 that should be
fixed). and clients would not get these fixes until it is promoted.
While there is no particular rush on these changes, it is good to get
anything that might block them out of the way.
-Andrew
Pascal Rapicault/Ottawa/[EMAIL PROTECTED]
Sent by: To
[EMAIL PROTECTED] Equinox development mailing
list <equinox-dev@eclipse.org>
cc
09/10/2007 09:54 AM
Subject
Re: [equinox-dev] [vote]
Please respond to graduating the new jar
Equinox development mailing list processor bundle
<equinox-dev@eclipse.org>
In the long, there is no discussion about doing this change. However the
benefits of doing it right away are not clear to me.
+0
PaScaL
From: Jeff McAffer/Ottawa/[EMAIL PROTECTED]
To: equinox-dev@eclipse.org
Date: 09/09/2007 11:07 PM
Subject: [equinox-dev] [vote] graduating the new jar processor bundle
As you may know, we used to have the JARProcessor embedded in the bowels of
Update manager. Turns out that there are several uses for the processor
(pack200 support, signing, verifying, ...) and having this function as a
stand-alone bundle would be "a good thing"(tm). So in the p2 work we did
just that and created org.eclipse.equinox.p2.jarprocessor. Bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=198564
talks about updating update to use the new processor. Of course, the
current JarProcessor bundle is in the Equinox Incubator. To date I think
we have avoided cases where we build the mainstream SDK based on content
from an incubator.
We have two choices, we can wait to move Update over or we can graduate the
current JARProcessor bundle. Here I popose the latter since the code in
the bundle is unchanged from the original that shipped in 3.3. All we are
doing is putting it in a separate bundle. The only thing at issue is the
shape of the API and that can evolve until the API freeze just as any other
bundle in HEAD.
So consider this a formal call for voting on graduating the
org.eclipse.equinox.p2.jarprocessor bundle.
+1 from me.
Jeff _______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: pic05568.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
