[ 
https://issues.apache.org/jira/browse/SLING-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler reopened SLING-6068:
-------------------------------------

There is another regression, the created artifacts now have different names, 
breaking any script. This is the output from version 1.4.4:

[INFO] --- slingstart-maven-plugin:1.4.4:package (default-package) @ 
org.apache.sling.launchpad ---
[INFO] Packaging standalone jar...
[INFO] Building zip: 
/Users/cziegeler/Developer/workspaces/granite/sling/launchpad/builder/target/org.apache.sling.launchpad-9-SNAPSHOT.jar
[INFO] Packaging webapp...
[INFO] Building zip: 
/Users/cziegeler/Developer/workspaces/granite/sling/launchpad/builder/target/org.apache.sling.launchpad-9-SNAPSHOT.war

and this from 1.4.5-SNAPSHOT:
[INFO] --- slingstart-maven-plugin:1.4.5-SNAPSHOT:package (default-package) @ 
org.apache.sling.launchpad ---
[INFO] Packaging standalone jar...
[INFO] Building zip: 
/Users/cziegeler/Developer/workspaces/granite/sling/launchpad/builder/target/org.apache.sling.launchpad-9-SNAPSHOT.standalonelaunchpad.jar
[INFO] Packaging webapp...
[INFO] Building zip: 
/Users/cziegeler/Developer/workspaces/granite/sling/launchpad/builder/target/org.apache.sling.launchpad-9-SNAPSHOT.webapplaunchpad.war


> slingstart-maven-plugin: Allow to start a quickstart JAR based on a 
> provisioning model even for non "slingstart" packagings
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-6068
>                 URL: https://issues.apache.org/jira/browse/SLING-6068
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Slingstart Maven Plugin 1.4.4
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Slingstart Maven Plugin 1.5.0
>
>         Attachments: SLING-6068-v01.patch
>
>
> Currently the {{slingstart-maven-plugin}} can only start a server based on 
> textual model definitions in case the maven module is of packaging 
> "slingstart" 
> (https://sling.apache.org/documentation/development/slingstart.html#starting-a-server).
>  
> For ITs it is often beneficial to have them in the same module as the tested 
> classes itself (which in most cases have packaging {{bundle}}). Therefore it 
> would be nice, if even for other packaging values all model definitions below 
> {{src/main/provisioning}} would be considered during the goal {{start}} 
> (which must first build the quickstart.jar out of the models and then start 
> it).
> Compare also with the readme in 
> https://github.com/apache/sling/blob/trunk/testing/samples/bundle-with-it/pom.xml#L196.
>  This would be especially helpful for ITs leveraging the {{TeleporterRule}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to