[
https://issues.apache.org/jira/browse/KARAF-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908545#comment-14908545
]
ASF GitHub Bot commented on KARAF-4020:
---------------------------------------
GitHub user roedll opened a pull request:
https://github.com/apache/karaf/pull/82
KARAF-4020: karaf-maven-plugin:archive doesn't respect an empty prefixPath
Fixes the issue described in KARAF-4020.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/roedll/karaf karaf-4020
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/karaf/pull/82.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #82
----
commit cd3448df56c71945030893f75d5d677871c0c4cf
Author: Lukas Roedl <[email protected]>
Date: 2015-09-25T19:12:23Z
Fix for issue KARAF-4020
----
> karaf-maven-plugin:archive doesn't respect an empty prefixPath
> --------------------------------------------------------------
>
> Key: KARAF-4020
> URL: https://issues.apache.org/jira/browse/KARAF-4020
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 4.0.1
> Reporter: Lukas Roedl
>
> The "archive" goal of the karaf-maven-plugin offers the possibility to modify
> the path prefix of files in the created archive (defaults to
> "${project.artifactId}-${project.version}").
> This seems to work for all cases except someone wants to set the pathPrefix
> to an empty string to actually disable the prefix.
> The cause of this is the fact that maven interprets the empty pathPrefix tag
> not as an empty string but as null and then uses the value given as
> defaultValue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
