stevedlawrence opened a new issue, #63: URL: https://github.com/apache/daffodil-sbt/issues/63
If a project implements a Daffodil layer, character set, or user defined function plugin, and enables the associated setting, then we add the appropriate Daffodil library as a dependency. This is necessary to compile the plugin. However, this means that any schema projects that depend on the layer/charset/udf plugin will now transitively pull in Daffodil as a dependency. In most cases, this doesn't really matter because the transitive dependencies will be overridden by daffodilVersion, or if you use `sbt "export fullClasspath"` to set DAFFODIL_CLASSPATH, the CLI will override any Daffodil dependencies. But it still clutters up the dependency list and makes it hard to see what the real dependencies our. We should add these daffodil dependencies to the "provided" scope so they exist for layer/charset/udf compilation, but does are not pulled in transitively. -- 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]
