Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] Tycho enforcer rules plugin



Note that something is probably wrong in the latest version 1.4

ð  requireSameVersions doesn’t seems to work

ð  I use 1.3


I had a quick look  :

-        Tycho add p2.eclipse-plugin: to each dependency (at least from what I understand with a mvn dependency:tree)

-        The enforcer plugin presume that dependency follow this pattern : // pattern is groupId[:artifactId[:type[:classifier]]]

(Check L107 here :

(Same code in 1.3 :


I believe that this rule will never work with tycho-plugin-eclipse.

Did I missed something ?

I think I have to code my own rule which will be specific to eclipse-plugin.



Benoit Maggi


De : tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] De la part de Jeff MAURY
Envoyé : mercredi 4 février 2015 15:31
À : Tycho developers list
Objet : Re: [tycho-dev] Tycho enforcer rules plugin


Assumed that Tycho represents OSGI dependencies as Maven dependencies, can't you use a Maven Enforcer plugin provided rule ?





On Wed, Feb 4, 2015 at 2:00 PM, MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:

Hi Tycho team,


I am looking for a Tycho plugin for enforcing some validation rules.

My need is to enforce the same version number for internal dependencies (in the same project)

I am looking for the Tycho version of this plugin :


I found this plugin (not in Tycho git repositories):


My questions :

-        Is there a way to enforce these type of rules with a Tycho plugin ?

-        Why the Sonatype plugin was not integrate in the first contribution to eclipse-tycho ?

See : The initial code based will be contributed by Sonatype, and is currently located at Github:

-        Is there any work in progress on the subject ?



Benoit Maggi

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




"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

Back to the top