The sling-org-apache-sling-feature-starter which is creating an executable JAR 
file is also using the sling-slingstart-feature-maven-plugin to later test the 
JAR file (for now it is starting it in a separate profile).

To build 'sling-org-apache-sling-feature-starter’ first the maven plugin must 
be built: 'sling-slingstart-feature-maven-plugin’ with:

        mvn clean install

Afterwards the 'sling-org-apache-sling-feature-starter’ can be built and the 
maven plugin can be test with:

        mvn clean install -P launch

To make the launch also stop the instance just comment out this line: 

Let me know if you run into any issues or want to suggest changes.

My next steps are to incorporate the logging from the instance back to starter 
and to clean up the migration.

- Andy

> On Jan 14, 2020, at 11:33 AM, Andreas Schaefer <schaef...@me.com.INVALID> 
> wrote:
> Hi
> I ran into a little snag with the Feature Starter Maven Plugin. Even though 
> the Sling Starter has a Control Listener to check the status and to stop it 
> after the launch from another process the Sling Launchpad Base creates a 
> MBean / MBean Startup Handler to check if the the service is up and running.
> As the Feature Launcher has no MBean Server integration I am going to change 
> the logic so that a Control Listener is created even w/o a Control Action so 
> that the it can be used to check if the server is up and running (status == 
> OK).
> Let me know if you think that the MBean Server integration (see Launchpad 
> Base DefaultStartupHandler) should be added and then I assume into the 
> Feature Launcher.
> - Andy

Reply via email to