You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2017/08/25 04:30:05 UTC
[jira] [Closed] (OAK-6533) Adjust test classpath order to reduce
number of error markers in Eclipse
[ https://issues.apache.org/jira/browse/OAK-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Jain closed OAK-6533.
--------------------------
Bulk close for 1.7.6
> Adjust test classpath order to reduce number of error markers in Eclipse
> ------------------------------------------------------------------------
>
> Key: OAK-6533
> URL: https://issues.apache.org/jira/browse/OAK-6533
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: examples, pojosr, solr
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Minor
> Fix For: 1.8, 1.7.6
>
>
> Some modules get error markers in Eclipse but they compile fine using Maven. This happens usually because of a limitation of the Eclipse + m2e classpath setup - when depending on another module dependencies are transitive. So for instance a dependency on {{oak-jcr}} will bring in {{jackrabbit-core}} and then {{lucene-core}} with version 3.6.0.
> Pending a fix in Eclipse proper, a viable workaround is to reorder the artifacts to ensure the ones that bring in the proper dependency are placed higher in the pom.xml .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)