Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] prep of 3.8 build for WindowBuilder

I do no know of any "3.7 vs 3.8" issues, but I so know the most common reason for md5 checksum issues after sign/pack/optimize is that you need to always finish that process with a "p2.process.artifacts" step.
I use an Ant call, similar to the following (of course, no pack="true" if that's already been done.


Maybe you already are doing something similar ... but, thought I'd share what I know.

Good luck.

From:        Mark Russell <mrrussell@xxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc:        Eric Clayberg <clayberg@xxxxxxxxxx>
Date:        09/07/2011 09:38 AM
Subject:        [cross-project-issues-dev] prep of 3.8 build for WindowBuilder
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

I'm running my 3.8 code through the same Python script I used to Sign/pack/optimize 3.7.  When I try to load the 3.8 update sites I get md5 sum errors but the 3.7 code loads fine.  Did the process change for 3.8?  If so is there a doc that describes it?

If not any ideas why the 3.7 code works fine but the 3.8 code does not?

Mark R Russell

(724) 473-3140
Release Engineer
Google Pittsburgh

cross-project-issues-dev mailing list

Back to the top