sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Süß <dominik.su...@gmail.com>
Subject Re: Failing with internal release for packageinit
Date Wed, 10 Oct 2018 14:20:08 GMT
Update:
This seems to fail in other locations as well - no clue how this works in
releases but:
mvn clean javadoc:jar source:jar install
org.codehaus.mojo:ianal-maven-plugin:verify-legal-files
on https://github.com/apache/sling-org-apache-sling-installer-core

Leads to the same problem.

Cheers
Dominik

On Wed, Oct 10, 2018 at 3:06 PM Dominik Süß <dominik.suess@gmail.com> wrote:

> Hi everyone,
>
> Karl somehow managed to get
> https://github.com/apache/sling-org-apache-sling-jcr-packageinit/ up and
> running and added the codebase from whiteboard.
> But when I tried to create an internal release I failed with
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1:verify-legal-files
> (verify-legal-files) on project org.apache.sling.jcr.packageinit: Artifact
> does not contain any legal files:
> org.apache.sling.jcr.packageinit-0.0.1-T20181010134901-51674eb-javadoc.jar
>
> The problem is that the META-INF directory in the javadoc.jar in contrast
> to the jar and sources.jar doesn't contain
> the maven-shared-archive-resources (which also contain the LICENSE file).
>
> Does anyone have an idea what's going on? I have nothing javadoc specific
> in and have no clue how to fix this.
>
> Cheers
> Dominik
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message