[
https://issues.apache.org/jira/browse/SLING-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-11524.
-------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-maven-plugin/commit/6af8d68cadc59964ceb640077be2ac513402e38d.
> install goal: Use always the artifact file from the underlying Maven project
> ----------------------------------------------------------------------------
>
> Key: SLING-11524
> URL: https://issues.apache.org/jira/browse/SLING-11524
> Project: Sling
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Sling Maven Plugin 2.4.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently goals "install-file" and "install" behave almost the same, the only
> difference is that the latter requires a project, but still picks up the
> bundle to install from the filesystem with a predefined path instead of
> leveraging the project's artifact(s) directly (irrespective of their
> path/name).
> Instead of relying on a certain path in the filesystem one should directly
> leverage {{MavenProject.getArtifact()}} and
> {{MavenProject.getAttachedArtifacts()}} (in that order) until a bundle file
> is found and remove the parameter {{bundleFileName}} altogether.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
