Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] 6 month release cycle

>The aggregation tests need only focus on overall integration whereby P2 compromises what is available leading to a completely missing bundle.
    p2 will never decide to *not* install a bundle just to get the rest to install... Do you have a scenario where this happen?
The remediation is about updating or uninstalling the elements that have been explicitely installed and it is *not* about tweaking the ranges that are in the metadata.

-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink
Sent: July-04-13 6:27 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] 6 month release cycle

Hi

On 04/07/2013 10:52, Alexey Panchenko wrote:
> Ideally, all the project tests should be executed - using dependencies 
> from the simultaneous release repository.

NO. Most project tests are to do with project functionality and so should be guaranteed passes on an aggregation. Dependencies on other projects should tested by the ptojects own build. The aggregation tests need only focus on overall integration whereby P2 compromises what is available leading to a completely missing bundle.  If every project test ran, the aggregation builds would take forever.
>
> Also, some checks of the compiled classes should be made (e.g. load 
> them all?), to verify that dependencies in the repository are 
> compatible with those used at compile time.
>
That's what the smoke test should do. Activate enough classes from enough places to demonstrate no CNFEs.

     Regards

         Ed Willink
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top