[
https://issues.apache.org/jira/browse/SLING-13075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-13075.
------------------------------------
Resolution: Fixed
https://github.com/apache/sling-feature-launcher-maven-plugin/commit/78f9d4b7036ccf134f0174910c24a11e5dc46d90
> feature-launcher-maven-plugin: Provide attached artifacts of current Maven
> build to launcher
> --------------------------------------------------------------------------------------------
>
> Key: SLING-13075
> URL: https://issues.apache.org/jira/browse/SLING-13075
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Feature Launcher Maven Plugin 1.0.4
>
>
> as discussed in
> https://lists.apache.org/thread/dcogmzq40cknj5sxxbmj2yjlbsjvkcfp, there is
> currently a problem using the feature launcher maven plugin to run a sling
> instance for integration test in a single POM scenario - artifacts attached
> to the current build and not yet stored in the local maven repo are not
> available to the feature launcher when running the ITs, as the the "install"
> phase takes place after the "integration-test" phase in maven.
> as a solution, we create a temporary directory before starting the feature
> launcher, store all attached artifacts there in maven2 repo layout, pass this
> as additional repository to the feature launcher, and remove it again when
> the launcher is stopped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
