[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875469#action_12875469 ] Konstantin Boudnik commented on HADOOP-6404: Thank Tom - looks like you've fixed HADOOP-6789 in the passing :-) Real nice! > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Tom White >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch, HADOOP-6404.patch, HADOOP-6404.patch, > HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872932#action_12872932 ] Hudson commented on HADOOP-6404: Integrated in Hadoop-Common-trunk #349 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/349/]) HADOOP-6404. Rename the generated artifacts to common instead of core. > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Tom White >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch, HADOOP-6404.patch, HADOOP-6404.patch, > HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872826#action_12872826 ] Hudson commented on HADOOP-6404: Integrated in Hadoop-Common-trunk-Commit #270 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/270/]) HADOOP-6404. Rename the generated artifacts to common instead of core. > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Tom White >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch, HADOOP-6404.patch, HADOOP-6404.patch, > HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[
https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869960#action_12869960
]
Chris Douglas commented on HADOOP-6404:
---
Unfortunately the patch no longer applies, but it looks good. +1
bq. I think renaming core-{default,site}.xml to common-{default,site}.xml
should be covered in another issue.
Agreed. Filed HADOOP-6783 and marked it for 0.21, but I agree that it wouldn't
be tragic if it slipped.
> Rename the generated artifacts to common instead of core
>
>
> Key: HADOOP-6404
> URL: https://issues.apache.org/jira/browse/HADOOP-6404
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
>Reporter: Owen O'Malley
>Assignee: Giridharan Kesavan
>Priority: Blocker
> Fix For: 0.21.0, 0.22.0
>
> Attachments: HADOOP-6404.patch, HADOOP-6404.patch
>
>
> In the project split we renamed Core to Common, but failed to change the
> artifact names. We should do it before 0.21.0 is released.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866959#action_12866959 ] Tom White commented on HADOOP-6404: --- Could someone review this please? > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch, HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863563#action_12863563 ] Hadoop QA commented on HADOOP-6404: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12443515/HADOOP-6404.patch against trunk revision 940527. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/495/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/495/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/495/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/495/console This message is automatically generated. > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch, HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863556#action_12863556 ] Tom White commented on HADOOP-6404: --- bq. Will you create a /common dist directory (i.e. http://archive.apache.org/dist/hadoop/core/) as well? I think so. There would be common, hdfs and mapreduce directories containing the tarballs. We might as a convenience also add a combined tarball to the core directory, using the script Owen created in HADOOP-6342. > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch, HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848814#action_12848814 ] Hadoop QA commented on HADOOP-6404: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12439593/HADOOP-6404.patch against trunk revision 926421. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 39 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/427/console This message is automatically generated. > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848813#action_12848813 ] Paolo Castagna commented on HADOOP-6404: Will you create a /common dist directory (i.e. http://archive.apache.org/dist/hadoop/core/) as well? > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848811#action_12848811 ] Paolo Castagna commented on HADOOP-6404: I am not sure if renamed files are correctly included in the patch. If not, how can I do that? > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > Attachments: HADOOP-6404.patch > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[
https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785179#action_12785179
]
Vinod K V commented on HADOOP-6404:
---
{{core-site.xml}} and {{core-default.xml}} need to be renamed too, so are other
build related directories. This issue will address them all or only the
artifacts?
> Rename the generated artifacts to common instead of core
>
>
> Key: HADOOP-6404
> URL: https://issues.apache.org/jira/browse/HADOOP-6404
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
>Reporter: Owen O'Malley
>Assignee: Giridharan Kesavan
>Priority: Blocker
> Fix For: 0.21.0, 0.22.0
>
>
> In the project split we renamed Core to Common, but failed to change the
> artifact names. We should do it before 0.21.0 is released.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6404) Rename the generated artifacts to common instead of core
[ https://issues.apache.org/jira/browse/HADOOP-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784899#action_12784899 ] Todd Lipcon commented on HADOOP-6404: - Perhaps also renaming src/test/core to src/test/common or even src/test/java would be a good idea now too. > Rename the generated artifacts to common instead of core > > > Key: HADOOP-6404 > URL: https://issues.apache.org/jira/browse/HADOOP-6404 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Owen O'Malley >Assignee: Giridharan Kesavan >Priority: Blocker > Fix For: 0.21.0, 0.22.0 > > > In the project split we renamed Core to Common, but failed to change the > artifact names. We should do it before 0.21.0 is released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
