policy: cleartk-* version numbers only in parent pom

On Thu, Mar 3, 2011 at 4:46 AM, Daryl <dlonnon@gmail.com> wrote:
> So I have the SHARP project which depends on 0.5.2-SNAPSHOT of
> cleartk, which is made up of cleartk-util and cleartk-syntax-opennlp
> (which happens to be depend on cleartk-util version 0.5.1). How would
> cleartk-syntax-opennlp even work if the interfaces changed in cleartk-
> util between versions?

I think this is a really important point - we need to make sure that users of 
ClearTK never get conflicting dependencies. I'd like to recommend the rule:

* Never declare a version number for a cleartk-* dependency. These versions 
must be inherited from the cleartk parent pom.

This would be true both within the various cleartk-* submodules, and also for 
externals users of cleartk. We would recommend that they always inherit from a 
specific version of the cleartk parent module, and let the cleartk-* versions 
be inherited from there.

I think this would guarantee that folks never get conflicting dependencies from 
ClearTK. Right?

The only downside to this rule is that you *must* have the cleartk pom as an 
ancestor of your parent pom. I don't think that's too much to ask to avoid 
dependency versioning hell... ;-)

If we agree to this, I'll update the documentation on how to declare a 
dependency on ClearTK.

Original issue reported on code.google.com by steven.b...@gmail.com on 4 Mar 2011 at 9:02

mkabbasi / cleartk

policy: cleartk-* version numbers only in parent pom #235