Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Tycho set-version does not modify all references to modified projects

Right my initial usecase was with lower bounds.

However I tested with strict versions (e.g. [3.2.0, 3.2.0]) and found that they were not updated either.

I filed the following bug in bugzilla "BugĀ 477328 - set-version mojo should update references for which lower bounds are matching the original version"

On Mon, Sep 14, 2015 at 9:40 AM Sievers, Jan <jan.sievers@xxxxxxx> wrote:
I guess you are talking about lower bounds of dependency ranges.
These should not be incremented automatically but adding an option to do
so probably makes sense


On 11/09/15 18:02, "tycho-user-bounces@xxxxxxxxxxx on behalf of Sebastien
Arod" <tycho-user-bounces@xxxxxxxxxxx on behalf of
sebastien.arod@xxxxxxxxx> wrote:

>I'm trying to use tycho set-version to change my version numbers.
>/set-version-mojo.html> states that "it consistently updates the version
>strings in the project's configuration files (e.g. pom.xml and
>META-INF/MANIFEST.MF) and all references to that project (e.g. in a
>However references from other bundles (using Require-Bundle) and
>references from fragment (using Fragment-Host) are not updated.
>Is this the expected behavior? Should I open an enhancement request on

tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top