Dependency on com.day.cq:parent:pom:82 in 6.5.6 uber-jar

[#1]

I'm unable to build projects after switching from uber-jar 6.5.5 to uber-jar 6.5.6. Maven is unable to find com.day.cq:parent:pom:82 artifact declared in 6.5.6 pom

<parent>
  <groupId>com.day.cq</groupId>
  <artifactId>parent</artifactId>
  <version>82</version>
</parent>

This section was no present in 6.5.5 uber-jar. Was correct uber-jar pom uploaded?

The same issue might apply to 6.4.8.2

[jakubg20913248 · Accepted solution]

Pom issue is resolved now and uber jar is posted with new dependency as follows:

<dependency>

      <groupId>com.adobe.aem</groupId>

      <artifactId>uber-jar</artifactId>

      <version>6.5.6-1.0</version>

       <scope>provided</scope>

</dependency>

[jakubg20913248 · Accepted solution]

Will apis without deprecations (like https://repo.adobe.com/nexus/content/repositories/public/com/adobe/aem/uber-jar/6.5.5/uber-jar-6.5.5...) be available? I see only apis-with-deprecations (https://repo.maven.apache.org/maven2/com/adobe/aem/uber-jar/6.5.6-1.0/uber-jar-6.5.6-1.0-apis-with-d...)?

[jakubg20913248 · Accepted solution]

OK, it looks like apis classifier is no longer required (https://repo.maven.apache.org/maven2/com/adobe/aem/uber-jar/6.5.6-1.0/uber-jar-6.5.6-1.0.jar)

[#5]

Uber jars are publicly available on maven central, it is the issue with uploaded pom which has incorrect dependency which Adobe is working to fix.

[#6]

Hey

Created a support case with Adobe customer care, and they pointed out that the way you're referencing the uber jar has changed. As outlined on the SP6 release notes, the new way to include the uber-jar is: 

<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.6-1.0</version> 
</dependency>

Hope this helps!

With kind regards

Koen