tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (TAP5-2052) tapestry-ioc has a compile dependency on tapestry-test
Date Thu, 14 Mar 2013 23:44:12 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship reassigned TAP5-2052:
------------------------------------------

    Assignee: Howard M. Lewis Ship
    
> 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
>
> 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

Mime
View raw message