4

Building Java DXA 1.7 for Web 8.5 following http://www.tridiondeveloper.com/using-and-debugging-dxa-java-with-web-8-5-on-amazon instructions to get a working java dxa 1.7 we have 34 errors in the Eclipse error log for plugin org.eclipse.m2e.logback.appender.

example:

"The POM for com.sdl.web:content-client-api:jar:8.5.0-1012 is missing, no dependency information available."

How do I resolve these warnings?

Addition error messages: enter image description here

| improve this question | | | | |
  • Can you please post those messages you get? And also I am curious if you can build this without Eclipse with pure Maven. You need Maven 3.2.2+ for this. – Alexey Mar 28 '17 at 14:01
4

Particularly this message:

"The POM for com.sdl.web:content-client-api:jar:8.5.0-1012 is missing, no dependency information available."

seems like an issue in libraries. Also it's interesting that apparently Eclipse has different mechanism of resolving Maven dependencies (but it's only a guess).

Fortunately, this one is easy to resolve. In WebApp's pom.xml you need to declare these dependencies:

<dependency>
    <groupId>com.sdl.web</groupId>
    <artifactId>cil</artifactId>
    <type>pom</type>
    <exclusions>
        <exclusion>
            <artifactId>content-client-api</artifactId>
            <groupId>com.sdl.web</groupId>
        </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>com.sdl.web</groupId>
    <artifactId>content-client-api</artifactId>
    <version>8.5.0-1013</version>
</dependency>

This excludes all content-client-api artifacts and includes it again with a right version.

| improve this answer | | | | |
  • Please can you be more specific. – Chris Mills Mar 30 '17 at 9:27
  • Please can you be more specific. This is already in the dependencyManagement section – Chris Mills Mar 30 '17 at 9:58
  • Do you mean you've added this to your Web App's pom.xml, but it doesn't help? – Rick Pannekoek Mar 31 '17 at 9:47
  • It was already in the POM dependencyManagement section. – Chris Mills Apr 3 '17 at 19:44
  • Is should rather be in <dependencies/> section. The fact you declare anything in dependencyManagement doesn't mean it's now used. You should declare a corresponding dependency. – Alexey Jun 1 '17 at 14:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.