[
https://issues.apache.org/jira/browse/DAFFODIL-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olabusayo Kilo reassigned DAFFODIL-2933:
----------------------------------------
Assignee: Olabusayo Kilo
> daffodil-test-integration does not include daffodil-test as a dependency
> ------------------------------------------------------------------------
>
> Key: DAFFODIL-2933
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2933
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Steve Lawrence
> Assignee: Olabusayo Kilo
> Priority: Major
>
> The daffodil-test-integration subproject includes tests that use jars built
> in the daffodil-udf, daffodil-cli, and daffodil-test subprojects. When some
> of these tests fork we set up the classpath correctly to reference jars in
> those classpaths.
> However, the build.sbt for daffodil-test-integration on has these
> dependencies:
> {code}
> .dependsOn(cli % "test->test", udf % "test->test"
> {code}
> So it only ensures daffodil-cli and daffodil-udf jars are built, but not
> daffodil-test jars. This means if you try to run
> daffodil-test-integration/test from a clean repo some tests will fail. We
> should add {{test % "test->test"}} to the integration dependsOn so those test
> jars are built.
> Note that a workaround is to just ensure the test jars are built by running
> "sbt daffodil-test/Test/compile" before running integration tests. Also,
> running normal tests first (e.g. "sbt test") will work too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
