On 13.11.2013 15:46, Richard Eckart de Castilho wrote: > We could also add our own dependency to app with a range between 1.0.0 and > 2.0.0, > as it is done for the other dependencies.
I have done that for the ruta plugins. At that time when I switched to maven, I was just happy to get it up and running. This remind me of the general problem with dependencies to eclipse bundles. Maybe felix will sometime be able to resolve them against p2 repositories... Peter > Although I'm as wary of ranges as I am of exclusions… to be honest, I'd prefer > simple fixed versions instead of ranges. Otherwise, your build tomorrow may > not > be the same as today (as we can see now). > > At least for a release, the versions should probably be fixed. There is a goal > which might do that, but I didn't every try it so far [1] > > -- Richard > > [1] > http://maven.apache.org/maven-release/maven-release-plugin/prepare-with-pom-mojo.html > > On 13.11.2013, at 15:42, Marshall Schor <m...@schor.com> wrote: > >> :-) >> >> Right... I'll post a little note to maven-dev to see if they want to look at >> fixing this, which breaks other builds too, I suspect, not just ours... >> >> I'm thinking we could fix this by excluding "app" - would need to test... >> >> -Marshall
