Closed tmortagne closed 10 years ago
What would you suggest changing it to? (I know enough maven to be dangerous, but certainly not enough to get everything right!)
What is the goal ?
The idea is to mark the vorbis-java-core test package as being needed when unit testing the vorbis-java-tika package, without vorbis-java-core test being included as a downstream dependency of vorbis-java-tika, and marking the test package as being already supplied (much as the main vorbis-java-core jar is). Is there a different scope to use to mark the dependency such?
Did you tried with just
Isn't this fixed by e8b27588021b5ad5b7117affaf6a6e2d79be5567
Yes seems to be fixed in 0.2 but 0.2 is not in Maven central and Tika 1.5 that was released yesterday still depends on 0.1.
I believe this is fixed in 0.3, which is present on Maven Central - any chance someone could check and confirm?
Great, thanks for you help. I've updated Tika to use 0.3, so hopefully it's all now fixed
Here is how the dependencu is declared:
It's the first time I see such a multiple scope.
Among other things it make the Maven WAR plugin include this dependency as if it was a build scope dependency.
I don't know if this worked in old version of Maven but org.apache.maven.model.Dependency has only one scope for sure.