[
https://issues.apache.org/jira/browse/SQOOP-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575016#comment-16575016
]
Hudson commented on SQOOP-3357:
-------------------------------
SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1193 (See
[https://builds.apache.org/job/Sqoop-hadoop200/1193/])
SQOOP-3357: Change MainframeImportTool to refer to MainframeManager (vasas:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=c3d916ab20ca02c9d6b85bb51d6c31eb31aaff88])
* (edit) src/java/org/apache/sqoop/tool/MainframeImportTool.java
* (edit) src/test/org/apache/sqoop/manager/TestMainframeManager.java
> Change MainframeImportTool to refer to MainframeManager class directly
> ----------------------------------------------------------------------
>
> Key: SQOOP-3357
> URL: https://issues.apache.org/jira/browse/SQOOP-3357
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.4.7
> Reporter: Nguyen Truong
> Assignee: Nguyen Truong
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: SQOOP-3357.patch
>
>
> Currently MainframeImportTool refers to the MainframeManager with a string
> which can create a problem in refactoring. It would be beneficial to change
> the string to a MainframeManager class reference.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
