[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500757#comment-17500757
]
Stefan Seifert commented on SLING-11168:
----------------------------------------
it seems the problem is already discussed in
https://github.com/ist-dresden/composum-nodes/issues/220 (discussion started
dec 2020!).
it was also bothering peregrine CMS:
https://github.com/headwirecom/peregrine-cms/issues/569
last comment from [~reusr1] was:
{quote}
this issue is now limited to windows 10 and some newer jvm's - the problem is
that some content from the initial bundle content are created as files instead
of a node structure - the problem is tracked as well in
ist-dresden/composum-nodes#220
{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
> 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)
