[
https://issues.apache.org/jira/browse/TAP5-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk reopened TAP5-2052:
--------------------------------
There still is a compile-time dependency from
org.apache.tapestry5.ioc.test.IOCTestCase.java to
org.apache.tapestry5.ioc.test.TestBase. Without adding tapestry-test as a
compile-time dependency, the build fails (at least in Eclipse, which correctly
doesn't include tapestry-test at compile time).
> tapestry-ioc has a compile dependency on tapestry-test
> ------------------------------------------------------
>
> Key: TAP5-2052
> URL: https://issues.apache.org/jira/browse/TAP5-2052
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Assignee: Howard M. Lewis Ship
> Priority: Blocker
> Fix For: 5.4
>
>
> For the `org.apache.tapestry5.ioc.test.IOCTestCase` class, there is a
> `compile` dependency on the `tapestry-test` project. This ends up as a
> compile dependency in the pom, so basically every Tapestry-based project has
> a compile dependency on `tapestry-test`.
> This could be fixed by changing the dependency back to the `provided`. On the
> other hand, test classes in the main source sets (like
> `org.apache.tapestry5.test.TapestryTestCase` in `tapestry-core`) seem a bit
> out-of-place anyway, so maybe they should be moved to `tapestry-test` and
> `tapestry-test` should depend on `tapestry-core`. I guess, gradle should be
> able to handle what looks like a circular dependency because of the different
> scopes. I haven't tried it though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
