[
https://issues.apache.org/jira/browse/OAK-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751939#comment-17751939
]
Manfred Baedke commented on OAK-10288:
--------------------------------------
[~reschke],
That is reasonable. When the compile phase runs in the subproject directory,
maven may assume that the dependencies are available in the repo. When it's run
in the parent directory, it has to assume that the oak-shaded-guava bundle
hasn't been installed yet.
> mvn test for oak-commons fails in top level directory, but not in project
> directory
> -----------------------------------------------------------------------------------
>
> Key: OAK-10288
> URL: https://issues.apache.org/jira/browse/OAK-10288
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: commons
> Reporter: Manfred Baedke
> Priority: Minor
>
> While
> {code:java}
> mvn clean install{code}
> is running fine,
> {code:java}
> mvn test{code}
> is failing due to
> {code:java}
> java.lang.ClassNotFoundException:
> org.apache.jackrabbit.guava.common.collect.Sets{code}
> , but only when run in the top level directory. It will succeed when run in
> the oak-commons project directory.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
