You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2021/07/12 20:54:00 UTC
[jira] [Updated] (SLING-10600) Add a mapping entry redirecting to
the project's top-level content path
[ https://issues.apache.org/jira/browse/SLING-10600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-10600:
------------------------------------
Summary: Add a mapping entry redirecting to the project's top-level content path (was: Add a mapping entry redirecting to the project's top-level content patch)
> Add a mapping entry redirecting to the project's top-level content path
> -----------------------------------------------------------------------
>
> Key: SLING-10600
> URL: https://issues.apache.org/jira/browse/SLING-10600
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Minor
> Fix For: Sling Project Archetype 1.0.6
>
>
> When a project created via the sling-project-archetype is deployed it creates an entry under {{/content/${contentFolderName}/home}} which is not easily accessible. We should create a mapping entry that redirects to that page, which is what many projects want.
> Since it can 'hijack' the front page we should not deploy it by default, but allow enabling it from the sample module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)