Using ${packaging.type} as value for packaging element in pom.xml of 0.9.11 prevents usage with sbt / ivy

The pom for 0.9.11 seems to be problematic for sbt / ivy. This is the change to pom.xml that causes the problem.

This is the error message I get:

[warn] 	[FAILED     ] org.reflections#reflections;0.9.11!reflections.${packaging.type}:  (0ms)
[warn] ==== local: tried
[warn]   /home/user/.ivy2/local/org.reflections/reflections/0.9.11/${packaging.type}s/reflections.${packaging.type}
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/org/reflections/reflections/0.9.11/reflections-0.9.11.${packaging.type}
[warn] ==== typesafe-releases: tried
[warn]   http://repo.typesafe.com/typesafe/releases/org/reflections/reflections/0.9.11/reflections-0.9.11.${packaging.type}
[warn] ==== typesafe-ivy-releasez: tried
[warn]   http://repo.typesafe.com/typesafe/ivy-releases/org.reflections/reflections/0.9.11/${packaging.type}s/reflections.${packaging.type}
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::              FAILED DOWNLOADS            ::
[warn] 	:: ^ see resolution messages for details  ^ ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: org.reflections#reflections;0.9.11!reflections.${packaging.type}
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::

[lhotari]

Found another workaround for sbt, adding this line to build.sbt helps:

sys.props += "packaging.type" -> "jar"

[Woodz]

This might help for the meanwhile: libraryDependencies += “org.reflections” %% “reflections” % “0.9.11” artifacts( Artifact(“reflections”, “”, “jar”))

Current 0.9.11 artifact in repo1 is w/o the ${packaging.type} variable (I’ve pushed it again, bad-bad-bad) And just committed (c328834) a fix to this (source head 0.9.12-SNAPSHOT)

@ronmamo there are some mirrors of the 0.9.11 artefact that still have this issue, which is causing sporadic issues. I am trying to identify them so that I can request that they delete the erroneous artefact, but to ensure that no mirrors or caches still have this issue, I strongly recommend creating a new release and encouraging your dependants to move to latest.