Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] api-check with tycho
Hi Mickael,

I was able to setup qualifiers, the trick was to add more to entries to "jgit.ignore" element.
And the latest release I have as a baseline was done with default timestamp providers, so now I have
[ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.5.1:compare-version-with-baselines (compare-attached-artifacts-with-release) on project org.eclipse.passage.lic.api: Version have
 moved backwards for (org.eclipse.passage.lic.api/0.6.0.v20191125-1440). Baseline has 0.6.0.v20191203-0807) with delta: 0.0.0
Well, I think the only way in this situation is just to go through all the bundles and features and increase the micro version.

What is still unclear for me: why "tycho-p2-plugin:1.5.1:p2-metadata " always reports  "No baseline version  "?
As I see it may happen if the call to "baselineService.getProjectBaseline" returns "null" from the call here
https://github.com/eclipse/tycho/blob/master/tycho-p2/tycho-p2-plugin/src/main/java/org/eclipse/tycho/plugins/p2/BaselineValidator.java#L88

Do you know how to persuade tycho that the given p2 update site contains baseline and should be used to replace the local artifact?

Thanks in advance,
AF

09.12.2019 13:59, Alexander Fedorov пишет:
Hi Mickael,

Thanks a lot for your answer! I'll try the trick with qualifiers. Do you think it will fix the "No baseline version" issue as well?

Actually I need both version and API checks, just started from the simpler one. And also the configuration in the platform aggregator is not decoupled enough to clearly understand the boundary between them :)

Thanks again,
AF

09.12.2019 13:10, Mickael Istria пишет:
Hi,

On Mon, Dec 9, 2019 at 10:37 AM Alexander Fedorov <alexander.fedorov@xxxxxxxxxx> wrote:
I'm trying to configure API check for Eclipse Passage project using Tycho. Currently it fails with the message
[ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.5.1:compare-version-with-baselines

Beware, compare-version-with-baselines isn't an API Check, it's a versioning check (it checks for no version moving backward and forces bumping versions after a release).

 (compare-attached-artifacts-with-release) on project org.eclipse.passage.lic.api: Only qualifi
er changed for (org.eclipse.passage.lic.api/0.6.0.v20191209-0913). Expected to have bigger x.y.z than what is available in baseline (0.6.0.v20191203-0807) -> [Help 1]                                            
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.5.1:compare-version-with-baselines (compare-attached-artifacts-with-release) on p
roject org.eclipse.passage.lic.api: Only qualifier changed for (org.eclipse.passage.lic.api/0.6.0.v20191209-0913). Expected to have bigger x.y.z than what is available in baseline (0.6.0.v20191203-0807)

Actually I do not expect it to fail here as there is no change in this bundle comparing to the last release baseline.

Build changes (like compiler settings, some volatile timestamp generation and so on) can lead to changes in the resulting jar even if there is no change in the source.
To ensure that for 1 given version of the source, the build would always result in the same jar, you also need to implement https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers in your build.
Then, coupled with version check, things usually work well.
 
HTH

_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tycho-dev


_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tycho-dev

Back to the top