You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Cédric Damioli (JIRA)" <ji...@apache.org> on 2015/05/07 12:39:00 UTC
[jira] [Updated] (JCR-3876) POM dependency to jackrabbit-data
test-jar is not test-scoped
[ https://issues.apache.org/jira/browse/JCR-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cédric Damioli updated JCR-3876:
--------------------------------
Summary: POM dependency to jackrabbit-data test-jar is not test-scoped (was: POM dependencies to jackrabbit-data test-jar are not test-scoped )
Noone objected
Committed in r1678160
> POM dependency to jackrabbit-data test-jar is not test-scoped
> --------------------------------------------------------------
>
> Key: JCR-3876
> URL: https://issues.apache.org/jira/browse/JCR-3876
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, jackrabbit-data
> Affects Versions: 2.7.5, 2.8, 2.9, 2.9.1, 2.10
> Reporter: Cédric Damioli
> Fix For: 2.10.1
>
>
> Since JCR-3729, jackrabbit-data POM exports test classes and jackrabbit-core POM use it without <scope>test</scope>
> It's certainly not a problem for maven users, but we use Ivy, and it seems that Ivy don't know how to manage two times the same dependency with the same scope, resulting in jackrabbit-data not being transitively get through jackrabbit-core.
> If I add <scope>tests</scope> to the dependency, all tests still run fine and Ivy becomes happy.
> Anybody objects ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)