[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500767#comment-17500767
]
Robert Munteanu commented on SLING-11168:
-----------------------------------------
Thanks for digging this up [~sseifert], it makes it much easier to understand
the problem. Perhaps we should consider switching to using the composum content
package(s), as indicated at
https://github.com/ist-dresden/composum-nodes/issues/220#issuecomment-809943639
:
{quote}With Releas 2.5.0 Composum Nodes is available as a package for
installation / upgrade via package manager. This installation via package
(composum-nodes-sling-package-<version>.zip) is the preferred solution for
future installations/upgrades of Composum Nodes. A 'setup' bundle is used to
remove an existing version of Composum Nodes before the installation of the new
version controlled by the 'setup' bundle starts. This should hopefully
eliminate the problems with the upgrade.
https://search.maven.org/search?q=a:composum-nodes-sling-package{quote}
> Sling Starter 12: Unable to launch Composum
> -------------------------------------------
>
> Key: SLING-11168
> URL: https://issues.apache.org/jira/browse/SLING-11168
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Affects Versions: Starter 12
> Reporter: Stefan Seifert
> Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> environment:
> * Windows 10
> * java 11.0.13 2021-10-19 LTS
> * Sling Starter: https://github.com/apache/sling-org-apache-sling-starter
> started sling starter 12 (or actually 13-SNAPSHOT from current master branch)
> with:
> {noformat}
> mvn clean install
> java -jar target/dependency/org.apache.sling.feature.launcher.jar -f
> target/slingfeature-tmp/feature-oak_tar.json
> {noformat}
> when trying to access composum via http://localhost:8080/bin/browser.html i
> get the normal sling login (if not logged in already) and login as
> admin/admin.
> directly after this i see a blink of composum, which is replaced immediately
> with another composum login dialog:
> [^image-2022-03-01-17-47-08-965.png]
> [^error.log] from the instance
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
