[
https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948177#comment-15948177
]
Robert Kanter commented on OOZIE-2849:
--------------------------------------
I checked the maven output, and it does get rid of all of the "Assembly file"
warnings.
However, when I listed all of the files recursively with and without the patch
after building and did a diff, it shows that the oozie script is now missing
when using the patch:
{noformat}
>> [5] 17:51 : oozie-git (master) :: diff /tmp/old.txt /tmp/new.txt
20d19
< distro/target/oozie-4.4.0-SNAPSHOT-distro/oozie-4.4.0-SNAPSHOT/bin/oozie
{noformat}
> Fix build warnings when assembling directories
> ----------------------------------------------
>
> Key: OOZIE-2849
> URL: https://issues.apache.org/jira/browse/OOZIE-2849
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Attila Sasvari
> Assignee: Attila Sasvari
> Priority: Trivial
> Attachments: OOZIE-2849-01.patch
>
>
> When building oozie we can observe a lot of warning
> {code}
> [WARNING] Assembly file:
> /Users/asasvari/workspace/apache/oozie_dup/tools/target/oozie-tools-4.4.0-SNAPSHOT-tools
> is not a regular file (it may be a directory). It cannot be attached to the
> project build for installation or deployment.
> {code}
> This behaviour can be explained by
> https://issues.apache.org/jira/browse/MASSEMBLY-628
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
