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 to produce p2 repositories with signed jars, so > sign step has to be pluggable to work with at least generic > jarsigner-plugin and Eclipse.org specific logic. > > -- > Regards, > Igor > > On 11-09-08 1:38 PM, Jesse McConnell wrote: >> >> 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<i...@ifedorenko.com> wrote: >>> >>> 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 11:57 AM, Benson Margulies wrote: >>>> >>>> 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 >>>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
