[JIRA] (WTOOL-92) Dependencies in start level 20 but no bundle is exporting these for that start level

[Himanshu Singhal (JIRA)]

Himanshu Singhal created WTOOL-92:
-------------------------------------

Summary: Dependencies in start level 20 but no bundle is exporting these for that start level
Key: WTOOL-92
URL: https://wcm-io.atlassian.net/browse/WTOOL-92
Project: wcm.io Tooling
Issue Type: Bug
Components: Maven
Reporter: Himanshu Singhal


During the project migration to cloud, we're getting the error while using `aem-analyser` plugin during local build.

{code:java}
io.wcm.wcm.commons.contenttype, com.adobe.acs.commons.mcp.util, io.wcm.handler.media.format, io.wcm.handler.url, io.wcm.sling.commons.request, io.wcm.sling.commons.resource, io.wcm.sling.commons.adapter, io.wcm.handler.url.spi, io.wcm.handler.richtext, io.wcm.handler.media.spi, io.wcm.handler.commons.dom, com.adobe.acs.commons.mcp.form, io.wcm.wcm.commons.util, org.jdom2, com.adobe.acs.commons.util, io.wcm.handler.media, io.wcm.sling.models.annotations, io.wcm.wcm.core.components.models, io.wcm.handler.link.type, io.wcm.handler.link.spi, com.adobe.acs.commons.models.injectors.annotation, io.wcm.handler.url.ui, io.wcm.wcm.parsys, io.wcm.handler.link] in start level 20 but no bundle is exporting these for that start level.
{code}


One way to fix project by adding these API in export bundle but my assumption is that since all dependencies are part of wcm io maven archetype (except acs commons dependencies) it should already be part of project build and explicit import shall not be required.

In that case, what could be the fix here instead of adding it explicitly in export packages for all dependencies?



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100188)

[Stefan Seifert (JIRA)]

[ https://wcm-io.atlassian.net/browse/WTOOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21461#comment-21461 ]

Stefan Seifert commented on WTOOL-92:
-------------------------------------

this start level is usually not controlled by the bundles itself, but by the paths in the content package that is used to deploy the bundles (although that feature is rarely used imho), see [https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#start-level-support-1|https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#start-level-support-1|smart-link]

please check if the bundles the package you are using to deploy are in a path like …/install/20 - and consider to move them up to the …/install folder.

> Dependencies in start level 20 but no bundle is exporting these for that start level

> ------------------------------------------------------------------------------------

[Stefan Seifert (JIRA)]

[ https://wcm-io.atlassian.net/browse/WTOOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21461#comment-21461 ]

Stefan Seifert edited comment on WTOOL-92 at 1/18/22 11:22 AM:
---------------------------------------------------------------

this start level is usually not controlled by the bundles itself, but by the paths in the content package that is used to deploy the bundles (although that feature is rarely used imho), see [https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#start-level-support|https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#start-level-support|smart-link]

please check if the bundles the package you are using to deploy are in a path like …/install/20 - and consider to move them up to the …/install folder.

was (Author: sseifert):

[Himanshu Singhal (JIRA)]

[ https://wcm-io.atlassian.net/browse/WTOOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21462#comment-21462 ]

Himanshu Singhal commented on WTOOL-92:
---------------------------------------

Bundles are deployed directly in install folder instead of any number folder and this issue wasn’t occurring previously. With the latest dependencies upgrade it started to happen.


There were other dependencies upgraded to latest version but nothing has changed in install folder.

{noformat} <groupId>io.wcm.maven</groupId>
<artifactId>io.wcm.maven.aem-global-parent</artifactId>
<version>2.0.0</version>{noformat}

[Himanshu Singhal (JIRA)]

[ https://wcm-io.atlassian.net/browse/WTOOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21462#comment-21462 ]

Himanshu Singhal edited comment on WTOOL-92 at 1/18/22 1:25 PM:
----------------------------------------------------------------

Bundles are deployed directly in install folder instead of any number folder and this issue wasn’t occurring previously. With the latest dependencies upgrade it started to happen.

There were other dependencies upgraded to latest version but nothing has changed in install folder.

was (Author: ug:079c51ef-2b84-4601-8aa7-dbf133d58c13):

[Himanshu Singhal (JIRA)]

[ https://wcm-io.atlassian.net/browse/WTOOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21463#comment-21463 ]

Himanshu Singhal commented on WTOOL-92:
---------------------------------------

Another point is it may show up for 3rd party dependencies but why it’s showing for all [http://wcm.io|http://wcm.io|smart-link] dependencies. It should already be embedded and we don’t explicitly embed or deploy as part of project.

[Stefan Seifert (JIRA)]

[ https://wcm-io.atlassian.net/browse/WTOOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21464#comment-21464 ]

Stefan Seifert commented on WTOOL-92:
-------------------------------------

i’ve never seen this warning myself - do you have an example project that shows the behavior?