You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/03/15 01:50:15 UTC

[jira] [Commented] (TAP5-2052) tapestry-ioc has a compile dependency on tapestry-test

    [ https://issues.apache.org/jira/browse/TAP5-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602962#comment-13602962 ] 

Hudson commented on TAP5-2052:
------------------------------

Integrated in tapestry-trunk-freestyle #1034 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1034/])
    TAP5-2052: Fix unwanted compiled dependency from tapestry-ioc to tapestry-test (Revision d1b22c9ff247c521b4dffbc1e053e1665091df69)

     Result = SUCCESS
hlship : 
Files : 
* tapestry-ioc/build.gradle

                
> 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