Re: [tycho-user] Problems with Reproducible Version Qualifiers.

[Simon Goodall <simon@xxxxxxxxxxxxxxxxxx>]

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 1.0.0.A.

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.

Regards,

Simon

On 23 November 2012 15:57, Paul Webster <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: org.eclipse.equinox.framework:org.eclipse.osgi.services:3.3.100-SNAPSHOT @ /shared/eclipse/builds/R4_2_maintenance/gitCache/eclipse.platform.releng.aggregator/rt.equinox.framework/bundles/org.eclipse.osgi.services/pom.xml: baseline and build artifacts have same version but different contents


[1] http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse-parent/pom.xml?h=R4_2_maintenance#n228

[2] http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse-parent/pom.xml?h=R4_2_maintenance#n272


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

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user