Re: [eclipse-pmc] PDE Build/UI Change for 3.4.1RC3

[Thomas Watson <tjwatson@xxxxxxxxxx>]

Maybe it is just me, but this sounds like a risky change for a point release. Especially after we have entered the RC stage of 3.4.1.

Chris, is this really low risk? How many tests do we have to ensure that no regressions will be introduced? Just curious, how many lines of code are being removed and are we sure the PDE-Build behavior gives us all the behavior we expect in this scenario?

Tom



"Chris Aniszczyk" ---09/08/2008 03:23:12 PM---(pde ui) product export from the ui does not generate bundles.info

From:	"Chris Aniszczyk" <caniszczyk@xxxxxxxxx>
To:	eclipse-pmc@xxxxxxxxxxx, "Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
Date:	09/08/2008 03:23 PM
Subject:	[eclipse-pmc] PDE Build/UI Change for 3.4.1RC3

---

(pde ui) product export from the ui does not generate bundles.info
https://bugs.eclipse.org/bugs/show_bug.cgi?id=240053

(pde build) product export from the ui does not generate bundles.info
https://bugs.eclipse.org/bugs/show_bug.cgi?id=246391

DESCRIPTION:
For a long time, PDE UI used its own code to export products. When p2 was added,
there was some differences between the way UI and Build generated certain artifacts
on export (mainly the config.ini). The lack of cohesion caused an issue in PDE UI to not 
support certain product configurations that use p2. To solve the issues on export when you're
using the UI,we will delegate to PDE Build to generate this artifact.


FIX:
-The fix is to delegate to PDE Build when building products.

RISKS:
-This is a low risk change.

PERFORMANCE IMPACT:
-none

-- 
Cheers,

~ Chris Aniszczyk_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc