You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See title. This can lead to problems when the bnd-[testing|export|resolve]-maven-plugin is used with resolve=true and failOnChanges=true, since it can cause non-deterministic failures of a build that previously built successfully.
I have even seen a scenario where the plugin demanded that I added a bundle to -runbundles in one build, and after doing so and rebuilding it demanded that I remove the same bundle I just added!
I expect this is an issue with non-determinism in the Felix resolver. The spec does not require the resolver to produce deterministic outputs -- only valid ones -- but likewise there is nothing in the spec that would prevent Felix from doing this.
The text was updated successfully, but these errors were encountered:
See title. This can lead to problems when the
bnd-[testing|export|resolve]-maven-plugin
is used withresolve=true
andfailOnChanges=true
, since it can cause non-deterministic failures of a build that previously built successfully.I have even seen a scenario where the plugin demanded that I added a bundle to -runbundles in one build, and after doing so and rebuilding it demanded that I remove the same bundle I just added!
I expect this is an issue with non-determinism in the Felix resolver. The spec does not require the resolver to produce deterministic outputs -- only valid ones -- but likewise there is nothing in the spec that would prevent Felix from doing this.
The text was updated successfully, but these errors were encountered: