Re: [cbi-dev] [jdt-core-dev] Fwd: compare artifacts to baseline version

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

On 12-07-05 10:03 AM, Stephan Herrmann wrote:
> On 07/05/2012 03:52 PM, Igor Fedorenko wrote:
> > I used jdt as an example to illustrate potential problem -- we have two
> > sets of artifacts that are built from the same sources but they are most
> > likely not byte-to-byte identical. Differences can be as benign as
> > different jar entry timestamps, but can be more serious, like different
> > jar signer certificates, different pack200 normalization, etc.
> >
> > So my question is, when the build cannot validate all project artifacts
> > against baseline, is it okay to mix artifacts produced by the build with
> > artifacts from the baseline or should we do something else?
>
> Would it help to explicitly specify a subset/superset relation?
>
> If o.e.jdt.core.jar has no changes
>   => none of the two subset artifacts require rebuilding
>
> If o.e.jdt.core.jar has changes but ant adapter doesn't
>   => safe not to rebuild ant adapter
>
> So, mixing an old ant adapter with a newer o.e.jdt.core.jar
> looks OK from my pov but not vice versa.

The build does not have access to the old ant adaptor, so the only two
options available are

1. use old o.e.jdt.core.jar with new ant adaptor and batch compiler
2. always use new o.e.jdt.core.jar, ant adaptor and batch compiler

If neither of these two options is 'okay', then providing baseline
repository for ant adaptor and batch compiler, as John suggested in
another reply, is the only way.

Also note that both batch compiler and ant adaptor are included in
pde/build feature, which I believe also requires o.e.jdt.core.jar, so
mixing old/new versions of the bundles during the build will result in a
mixture of old/new bundles at runtime.

--
Regards,
Igor