Details
-
Bug
-
Resolution: Workaround exists
-
Neutral
-
None
-
6.1.2
-
None
Description
Steps to reproduce
From your pom.xml apart add magnolia-content-indexer latest version, 6.1.2, and then add any library whose groupId is info.magnolia.solr. For instance:
<dependency>
<groupId>info.magnolia.solr</groupId>
<artifactId>magnolia-content-indexer</artifactId>
<version>6.1.2</version>
<exclusions>
<exclusion>
<groupId>org.apache.tika</groupId>
<artifactId>tika-parsers</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>info.magnolia.solr</groupId>
<artifactId>magnolia-solr-search-provider</artifactId>
<version>6.1.2</version>
<exclusions>
<exclusion>
<groupId>org.apache.tika</groupId>
<artifactId>tika-parsers</artifactId>
</exclusion>
</exclusions>
</dependency>
In this case the library magnolia-solr-search-provider also brings the old magnolia-content-indexer 6.1.1 and there is a compilation error.
Expected results
mvn clean install works well
Actual results
There is actually a compilation error:
Failure to find info.magnolia.maven.poms-internal:magnolia-parent-pom-internal:pom:50 in https://ci-repo.aexp.com/java-proxy/content/groups/prod was cached in the local repository, resolution will not be reattempted until the update interval of prod has elapsed or updates are forced
Workaround
When adding, for the above example, magnolia-solr-search-provider artifactId also exclude the magnolia-content-indexer. So the it looks like this:
<dependency>
<groupId>info.magnolia.solr</groupId>
<artifactId>magnolia-solr-search-provider</artifactId>
<version>6.1.2</version>
<exclusions>
<exclusion>
<groupId>org.apache.tika</groupId>
<artifactId>tika-parsers</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.solr</groupId>
<artifactId>magnolia-content-indexer</artifactId>
</exclusion>
</exclusions>
</dependency>
Note the magnolia-content-indexer exclusion needs to be done for every library whose groupId is info.magnolia.solr (magnolia-solr-search-provider, magnolia-solr-templating, magnolia-solr-workbench, magnolia-solr-ui)
Dev notes
This happens when using dx-core's parent pom to manage Magnolia Solr module dependencies. 6.2.26 parent pom manages Solr module 6.1.1 version which is affected by a known issue.
Magnolia 6.2.27 will have this sorted out properly and until then the workaround mentioned above can be used.