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. |
||
|---|---|---|
| .. | ||
| 1.0.0 | ||
| 1.0.3 | ||
| 1.1.2 | ||
| 1.1.4 | ||
| 1.1.5 | ||
| 1.2.0 | ||
| 1.3.0 | ||
| 1.6.0 | ||
| 1.7.0 | ||
| 1.8.0 | ||
| 2.0.0 | ||
| 0.10.0.markdown | ||
| 0.10.1.markdown | ||
| 0.11.0.markdown | ||
| 0.11.3.markdown | ||
| 0.13.6.markdown | ||
| 0.13.7.markdown | ||
| 0.13.8.markdown | ||
| 0.13.9.markdown | ||
| 0.13.11.markdown | ||
| 0.13.12.markdown | ||
| 0.13.13.markdown | ||
| 0.13.14.markdown | ||
| 0.13.16.markdown | ||
| 1.0.0.markdown | ||
| 1.0.1.markdown | ||
| 1.0.2.markdown | ||
| 1.0.3.markdown | ||
| 1.0.4.markdown | ||
| 1.1.0.markdown | ||
| 1.1.1.markdown | ||
| about.markdown | ||
| sample.md | ||