[
https://issues.apache.org/jira/browse/SQOOP-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bilung Lee updated SQOOP-371:
-----------------------------
Description:
1. Create the new package under org.apache.sqoop namespace.
2. Move logics from com.cloudera.sqoop classes to org.apache.sqoop classes.
3. Let com.cloudera.sqoop classes inherit logics from org.apache.sqoop classes.
4. Deprecate classes under com.cloudera.sqoop namespace.
Also remove copyright notice in the header.
(http://www.apache.org/legal/src-headers.html)
NOTE that checkstyle is revised to accommodate the license header
without copyright. As a result, it will complain all other files until
they are also migrated with the new license header (without copyright).
was:
1. Create the new package under org.apache.sqoop namespace.
2. Move logics from com.cloudera.sqoop classes to org.apache.sqoop classes.
3. Let com.cloudera.sqoop classes inherit logics from org.apache.sqoop classes.
4. Deprecate classes under com.cloudera.sqoop namespace.
Also remove copyright notice in the header.
(http://www.apache.org/legal/src-headers.html)
> Migrate util package to new name space
> --------------------------------------
>
> Key: SQOOP-371
> URL: https://issues.apache.org/jira/browse/SQOOP-371
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Bilung Lee
> Assignee: Bilung Lee
>
> 1. Create the new package under org.apache.sqoop namespace.
> 2. Move logics from com.cloudera.sqoop classes to org.apache.sqoop classes.
> 3. Let com.cloudera.sqoop classes inherit logics from org.apache.sqoop
> classes.
> 4. Deprecate classes under com.cloudera.sqoop namespace.
> Also remove copyright notice in the header.
> (http://www.apache.org/legal/src-headers.html)
> NOTE that checkstyle is revised to accommodate the license header
> without copyright. As a result, it will complain all other files until
> they are also migrated with the new license header (without copyright).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
