The creation review has gone through for both Aether and Sisu. I have also just
submitted the project provisioning requests.
I'll work with Denis at Eclipse to get the provisioning done as quickly as
possible so we can do the necessary work to run out releases of Sisu and Aether
and therefore
Igor,
1. neither pack nor sign
package jar
generate p2 metadata
I'm looking at a P2 site from Tycho, and the only P2 stuff I see is
the XML files at the top level. Is there anything that actually goes
into the jar?
--benson
artifacts.xml contains md5 checksums of the artifact files. Signing or
pack200 conditioning changes file contents and thus invalidates the
checksums. In other words, artifacts.xml can only be generated after
final signed/packed version of the files has been created.
--
Regards,
Igor
On 11-09-08
and the actual process is
pack
sign (currently can only be done on build.eclipse.org)
repack
then fix checksums and insert some extra metadata in the
artifact.xml/artifact.jar file
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Thu, Sep 8, 2011 at 12:30, Igor Fedorenko
The whole point of this discussion is to find a good way to eliminate
artifacts.xml fixup step at the end.
Also note that Eclipse.org is not the only
organization that needs to produce p2 repositories with signed jars, so
sign step has to be pluggable to work with at least generic
Thanks, I now feel that I have the picture.
On Thu, Sep 8, 2011 at 1:45 PM, Igor Fedorenko i...@ifedorenko.com wrote:
The whole point of this discussion is to find a good way to eliminate
artifacts.xml fixup step at the end.
Also note that Eclipse.org is not the only
organization that needs
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357130
this deals with this issue somewhat, at least there are supposed to be
some p2 tooling for this
if your working on the tooling for tycho to be able to do this then I
can hold off on this sort of integration for the hackish signing
plugin
Issue Subscription
Filter: Design Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
https://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
