mirror of https://github.com/sbt/sbt.git
73d164fa84
**Problem** In an Ivy resolver pattern, the [organisation]/[organization] token has its dots rewritten to slashes (org.example → org/example), behaving like Ivy's [orgPath] token rather than being literal. Per the [Apache Ivy spec](http://ant.apache.org/ivy/history/latest-milestone/concept.html), [organisation] should be substituted literally and [orgPath] is the slash-separated form. Root cause: Patterns.isMavenCompatible defaulted to true, which sbt forwards to Apache Ivy as setM2compatible(true); with m2-compatibility on, Ivy rewrites the [organisation] token to slash form. A user supplying a custom Ivy pattern (e.g. for an SFTP/SSH resolver) inherited that default and got the wrong paths, with no obvious indication why. The only workaround was the non-obvious withIsMavenCompatible(false). **Solution** Flip the default of Patterns.isMavenCompatible from true to false, so a hand-written Patterns keeps [organisation] literal by default — matching the Ivy spec. |
||
|---|---|---|
| .. | ||
| cache-version.md | ||
| dependency-tree-dedup.md | ||
| migration.md | ||
| missing-file-error.md | ||
| parallel-dependency-resolution.md | ||
| parallel-resolution-supershell.md | ||
| patterns-maven-compatible-default.md | ||
| remote-project-update.md | ||