[
https://issues.apache.org/jira/browse/OAK-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751973#comment-17751973
]
Julian Reschke commented on OAK-10288:
--------------------------------------
bq. One way to solve it: use released version of the shaded jar for the
dependencies of the other subprojects. I guess that even makes sense, the
shaded jar only needs to change when the Guave version changes.
That would be equivalent to releasing it independently.
There are two drawbacks with that:
1. Additional complexity
2. We'd need a mechanism to ensure that all Oak subprojects actually use the
same version.
> 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)
