Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Problems with Reproducible Version Qualifiers.

There was a long discussion whether Tycho should attempt to identify
identical artifacts even when versions changes, i.e. 1.0.0.A and 1.0.0.B
in your example, in one of CBI bugzillas. In the end we decided it was
too hard a problem, and would likely result in unstable/unpredictable

What was implemented in Tycho essentially enforces "same id/version ==
same contents" policy for p2 artifacts produced by Tycho builds. Changes
to version disable this validation and forcing new version, with an
artificial commit, for example, provides developers with a way to force
new artifact contents even if Tycho believes nothing changed.

Git timestamp provider calculates build timestamp from the most recent
commit that touches any file under project basedir. Doing this on
repository level is too coarse-grained and would pretty much render this
feature useless.

Also note that git timestamp provider allows ignore of files based on
includes/excludes filter. I believe proper stable versions require
filtering of pom.xml files and other source resources that control build
output but are usually not part of project "real" functionality.


On 12-11-26 5:22 AM, Simon Goodall wrote:
Thanks Paul,

That's different to the view I had of the baseline repository. I had
somehow to to the idea that given version 1.0.0.A and 1.0.0.B, if the
two plugins were identical, then 1.0.0.B would be replaced by version

I'm currently looking at implementing a timestamp provider for
mercurial. I have something working which provides a timestamp based on
the latest commit for the repository, not the individual project. Is
that the correct behaviour - or is tycho-dev better for this question?
The doc for the git timestamp provider indicates the timestamp is for
the whole repository. This is probably why I thought the baseline
repository would replace 1.0.0.B with 1.0.0.A in the case where the
plugin is otherwise identical.



On 23 November 2012 15:57, Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx
<mailto:pwebster@xxxxxxxxxxxxxxxxxxx>> wrote:

    The configuration we use for qualifiers [1] and baseline comparator [2].

    If the plugin/version/qualifier is not in the p2 repo specified in
    [2] then you should get a message stating there's no baseline
    version MavenProject.  But if the id/version/qualifier match exactly
    you should get something like:

    [WARNING] MavenProject:
    baseline and build artifacts have same version but different contents



    Paul Webster
    Hi floor.  Make me a sammich! - GIR

    tycho-user mailing list
    tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>

tycho-user mailing list

Back to the top