Even if fully-qualified versions are used, is there anything to stop someone from rebuilding bundles with changed content but reusing the same version and qualifier? This is bad practice but I've heard of projects (not at Eclipse) doing it and it would mean the only way to absolutely guarantee immutability is for the aggregator to only pull bundles from the update site when the aggregation file changes (as David suggested above).
Sam -- Sam Davis Software Engineer, Tasktop Dev Committer, Eclipse Mylyn http://tasktop.com On Mon, Jan 11, 2016 at 7:01 AM, Doug Schaefer <[email protected]> wrote: > You can call them being lazy, but I call it being understaffed/underfunded. > > While I agree with the technicalities of your argument Mickael, we have > also been very careful on the planning council not to put too much burden > on the projects. Forcing them to update all the versions they have in the > b3 agg file on every build is a non starter. We need to manage the balance > between the value of projects joining simrel against the costs. It's not > automatic. > > - Doug. > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
