[
https://issues.apache.org/jira/browse/BUILDR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655191#action_12655191
]
Ittay Dror commented on BUILDR-225:
-----------------------------------
also, it looks like using the include method above does not behave as
ArchiveTask#include, in that the full path of the entry is included in the
archive, not just the base name. it would be nice if Merge#include would have
the same spec as ArchiveTask#include
> ArchiveTask#merge, not according to doc
> ---------------------------------------
>
> Key: BUILDR-225
> URL: https://issues.apache.org/jira/browse/BUILDR-225
> Project: Buildr
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.3.4
>
>
> The doc says
> # Returns an object that supports two methods: include and exclude. You can
> use these methods to merge
> # only specific files. For example:
> # zip(..).merge('src.zip').include('module1/*')
> but the implementation is:
> source.entries.reject { |entry| entry.directory? }.each do |entry|
> if @includes.any? { |pattern| File.fnmatch(pattern, entry.name,
> File::FNM_PATHNAME) } &&
> [EMAIL PROTECTED] { |pattern| File.fnmatch(pattern,
> entry.name, File::FNM_PATHNAME) }
> so it doesn't check directories, only files. so if the zip has
> module1/src/Foo.java, the pattern 'module1/*' will not match and the file
> will not be included
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
