You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2015/10/20 09:02:27 UTC

[jira] [Commented] (STANBOL-1444) Sling 8 release breaks Stanbol Build

    [ https://issues.apache.org/jira/browse/STANBOL-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964675#comment-14964675 ] 

Rupert Westenthaler commented on STANBOL-1444:
----------------------------------------------

This is caused by the {{maven-launchpad-plugin}} that (as a default) uses the current release for the {{org.apache.sling:org.apache.sling.launchpad}} to read the default bundle list.

However as Stanbol does not include the default bundle those feature should be deactivated in the first place. So the solution is to find out why this feature is not deactivated as supposed.

After some digging in the source of the {{maven-launchpad-plugin}} it turned out that the plugin does read the {{includeDefaultBundles}} not from the configuration element of the {{prepare-package}} execution but directly from the configuration of the plugin.

This means that all current Stanbol Launchers need to be adapted like the following example shows

{code:xml}
      <plugin>
        <groupId>org.apache.sling</groupId>
        <artifactId>maven-launchpad-plugin</artifactId>
        <executions>
          <execution>
            <id>prepare-package</id>
            <goals>
              <goal>prepare-package</goal>
            </goals>
            <configuration>
              <!-- not used - define directly in the plugin configuration
              <includeDefaultBundles>false</includeDefaultBundles>
               -->
              [..]
            </configuration>
          </execution>
        </executions>
        <configuration>
          <includeDefaultBundles>false</includeDefaultBundles>
          <defaultBundleList>
            [..]
          <defaultBundleList>
        </configuration>
{code}

> Sling 8 release breaks Stanbol Build
> ------------------------------------
>
>                 Key: STANBOL-1444
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1444
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Launcher 
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 1.0.0, 0.12.1
>
>
> The release of [Sling 8 | http://sling.apache.org/news/sling-launchpad-8-released.html] broke the Stanbol build as the maven lauchpad plugin now tries to download the default bundle list of Sling 8. However with Sling 8 the project switched from the bundlelist to the new slingstart feature. So their is no default bundlelist for Sling 8. This results in the following error.
> {code}
> [ERROR] Failed to execute goal on project org.apache.stanbol.launchers.full: Could not resolve dependencies for project org.apache.stanbol:org.apache.stanbol.launchers.full:jar:0.12.1-SNAPSHOT: Could not find artifact org.apache.sling:org.apache.sling.launchpad:xml:bundlelist:8 in central (http://repo1.maven.org/maven2) -> [Help 1]
> {code}
> For more Information see the following Mail Threads
> * [dev@stanbol.apache.org | http://markmail.org/message/t7vivwineu5s7cph]
> * [dev@sling.apache.org | http://sling.markmail.org/thread/lfxpfm6agflp3fmd]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)