stevedlawrence commented on issue #146:
URL: https://github.com/apache/daffodil-sbt/issues/146#issuecomment-3665514117
> Fortunately plugins are just jars, so they work like a normal dependency
with SBT. It's just the saved parsers that need extra help as far as I'm aware.
With the latest snapshot of sbt-daffodil, it's actually a bit more
complicated. Plugins are now are published with a "daffodilXYZ" classifier, so
depending on them requires adding that classifier. This can be done manually,
e.g.
```scala
libraryDependencies ++= Seq(
"com.example" % "dfdl-layer" % "0.0.1" % "provided"
withClassifier("daffodil400")
)
```
But using daffodilPluginDependnecies is preferred since it does that
automatically. It also marks plugin dependencies as "provided", which is
important so that schemas dont' depend on a specific version of a plugin--this
is important so we don't transitively pull in the wrong plugin version.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
