[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945948#comment-15945948 ] Robert Kanter commented on OOZIE-2849: -- I've moved this to a subtask of OOZIE-1702 because this JIRA is fixing one of the types of build warnings that we categorized there. > 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)
[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946186#comment-15946186 ] Hadoop QA commented on OOZIE-2849: -- Testing JIRA OOZIE-2849 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [hadooplibs/hadoop-utils-2]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 1906 .Tests rerun: 29 .Tests failed at first run: org.apache.oozie.coord.TestCoordUtils,org.apache.oozie.command.wf.TestSubmitPigXCommand,org.apache.oozie.client.TestLocalOozie,org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC,org.apache.oozie.command.coord.TestCoordActionsKillXCommand, {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/3744/ > 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)
[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ 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)
[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954766#comment-15954766 ] Attila Sasvari commented on OOZIE-2849: --- [~gezapeti] can you take a look? thanks! > 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, OOZIE-2849-02.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)
[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954897#comment-15954897 ] Hadoop QA commented on OOZIE-2849: -- Testing JIRA OOZIE-2849 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [hadooplibs/hadoop-utils-2]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} .Tests run: 1906 .Tests failed: 5 .Tests errors: 3 .The patch failed the following testcases: . testMain(org.apache.oozie.action.hadoop.TestHiveMain) . testPigScript(org.apache.oozie.action.hadoop.TestPigMain) . testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain) . testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain) . testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI) .Tests failing with errors: . testAddXIncludeFromStream(org.apache.oozie.util.TestXConfiguration) . testAddXIncludeFromReader(org.apache.oozie.util.TestXConfiguration) . testLoadDump(org.apache.oozie.tools.TestDBLoadDump) {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/oozie-trunk-precommit-build/3769/ > 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, OOZIE-2849-02.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)
[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955922#comment-15955922 ] Robert Kanter commented on OOZIE-2849: -- I think it should be fine as long as we do it in a major release (i.e. 5.0.0) because it could break someone's deployment flow if they had previously been grabbing the directories and not the archives. > 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, OOZIE-2849-02.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)
[jira] [Commented] (OOZIE-2849) Fix build warnings when assembling directories
[ https://issues.apache.org/jira/browse/OOZIE-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064606#comment-16064606 ] Peter Cseh commented on OOZIE-2849: --- +1 Decreasing the number of warnings in the build is a good thing. > 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, OOZIE-2849-02.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.4.14#64029)