[
https://issues.apache.org/jira/browse/KARAF-6828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190140#comment-17190140
]
ASF subversion and git services commented on KARAF-6828:
--------------------------------------------------------
Commit a4dd2a72c31eeb48dca737825e34fd91da1d1e3d in karaf's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=a4dd2a7 ]
Merge pull request #1177 from jbonofre/KARAF-6828
[KARAF-6828] Add fallback to artifact
${project.build.directory}/${project.build.finalName}.jar in the karaf:run goal
> Ensure karaf:run (maven goal) can find a pre-built artifact
> -----------------------------------------------------------
>
> Key: KARAF-6828
> URL: https://issues.apache.org/jira/browse/KARAF-6828
> Project: Karaf
> Issue Type: Task
> Components: karaf
> Reporter: Romain Manni-Bucau
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.3.0, 4.2.10
>
>
> Issue: when launching "mvn package && mvn karaf:run" - the important part
> being the fact the karaf:run is decoralated from the build command,
> RunMojo#deploy does not find the bundle to deploy.
> Would be neat to have a fallback on
> ${project.build.directory}/${project.build.finalName}.jar to let karaf:run be
> able to work without having to pay any build time (awesome for demo not
> requiring a features.xml ;)).
>
> Affected version is 4.3.0.RC1 (dont think it is in Jira yet).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
