[SLING-11099] JSPC plugin missing critical dependencies by default

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JSPC Maven Plugin 2.3.2
• Fix Version/s: JSPC Maven Plugin 2.3.4
• Component/s: Maven Plugins and Archetypes
• Assignee: Karl Pauls
• Reporter: Donal Fellows
• Created: 28/Jan/22 16:22
• Updated: 12/Apr/22 10:53
• Resolved: 28/Jan/22 21:54

Description

The JSPC Maven Plugin, version 2.3.2, fails to work when used as an ordinary Maven plugin. The first two lines of relevance (there's a lot more stack trace, but it is really not very informative) from the build logs are:

{{{}[WARNING] Error injecting: org.apache.sling.maven.jspc.JspcMojo
{}}}java.lang.NoClassDefFoundError: org/apache/sling/feature/ArtifactId

The problem appears to be that the org.apache.sling.feature dependency (and, by transitive closure, the org.osgi.framework dependency as well) is marked as provided. Adding the following two as explicit plugin dependencies is a workaround (and allows at least my builds to work). However, I do not believe that ordinary Maven users should have to do such a workaround.

  <dependency>
      <groupId>org.apache.sling</groupId>
      <artifactId>org.apache.sling.feature</artifactId>
      <version>1.2.30</version>
  </dependency>
  <dependency>
      <groupId>org.osgi</groupId>
      <artifactId>org.osgi.framework</artifactId>
      <version>1.10.0</version>
  </dependency>

Note that 2.3.0 worked correctly.

Issue Links

• is broken by: SLING-10887 Optionally allow osgi dependencies provided by a feature