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

Konrad Windszus edited comment on SLING-9729 at 7/26/21, 12:13 PM:
-------------------------------------------------------------------

I would only add pluginMgmt, so every Maven module must opt-in by referencing 
the plugin {{bnd-resolver-maven-plugin}}. 
It seems that although the distro instruction 
(https://bnd.bndtools.org/instructions/distro.html) seems to be more suitable, 
creating a distro from Sling Starter has no Maven tooling support right now ( 
https://github.com/bndtools/bnd/issues/4476).
So let's start with the {{bnd-resolver-maven-plugin}} and a local bndrun file 
looking like this

{code}
-standalone: ${fileuri;${.}/target/index.xml}

-runfw: org.apache.felix.framework
-runee: JavaSE-1.8

-resolve.effective: active
{code}




was (Author: kwin):
I would only add pluginMgmt, so every Maven module must opt-in by referencing 
the plugin {{bnd-resolver-maven-plugin}}. 
It seems that although the distro instruction 
(https://bnd.bndtools.org/instructions/distro.html) seems to be more suitable, 
creating a distro from Sling Starter has no Maven tooling support right now.
So let's start with the {{bnd-resolver-maven-plugin}} and a local bndrun file 
looking like this

{code}
-standalone: ${fileuri;${.}/target/index.xml}

-runfw: org.apache.felix.framework
-runee: JavaSE-1.8

-resolve.effective: active
{code}

 https://github.com/bndtools/bnd/issues/4476

> Bundle-Parent: Check if resolvable against latest Sling Starter
> ---------------------------------------------------------------
>
>                 Key: SLING-9729
>                 URL: https://issues.apache.org/jira/browse/SLING-9729
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>    Affects Versions: Bundle Parent 39
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Bundle Parent 44
>
>
> With SLING-9491 an OSGi repository index is being generated for Sling 
> Starter. Every bundle should be resolvable against that repository index (to 
> ensure compatibility with the latest Sling Starter).
> To achieve that an approach like in 
> https://github.com/apache/jackrabbit-filevault/blob/0b3c4cb5a99d14e3d0ae881d7864806ed950c622/parent/pom.xml#L177
>  should be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to