You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2026/01/13 10:24:00 UTC
[jira] [Closed] (SLING-13038) sling-feature-launcher-maven-plugin: Make process tracker configurable
[ https://issues.apache.org/jira/browse/SLING-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert closed SLING-13038.
----------------------------------
> sling-feature-launcher-maven-plugin: Make process tracker configurable
> ----------------------------------------------------------------------
>
> Key: SLING-13038
> URL: https://issues.apache.org/jira/browse/SLING-13038
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
> Affects Versions: Feature Launcher Maven Plugin 1.0.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Feature Launcher Maven Plugin 1.0.2
>
>
> currently, each time the "start" goal is executed, a process tracker is hooked into the java runtime to ensure the sling instance is killed forcibly if it was not stopped properly during the maven build.
> that is fine for CI/CD environments, but when debugging locally, you sometimes would like to have a profile to keep it running after the build completes for debugging purposes.
> solution: introduce a configuration option to disable this process tracking, but keep it enabled by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)