[ 
https://issues.apache.org/jira/browse/SQOOP-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218161#comment-14218161
 ] 

ASF subversion and git services commented on SQOOP-1754:
--------------------------------------------------------

Commit abd12fa544bda54a22450741717d8c01d202c977 in sqoop's branch 
refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=abd12fa ]

SQOOP-1754: Sqoop2: Remove JarUtil class

(Qian Xu via Jarek Jarcec Cecho)


> Sqoop2: Remove JarUtil class
> ----------------------------
>
>                 Key: SQOOP-1754
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1754
>             Project: Sqoop
>          Issue Type: Sub-task
>    Affects Versions: 1.99.4
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Qian Xu
>              Labels: newbie
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1754.2.patch, SQOOP-1754.patch
>
>
> We're currently using 
> {{[JarUtil|https://github.com/apache/sqoop/blob/sqoop2/connector/connector-sdk/src/main/java/org/apache/sqoop/connector/common/JarUtil.java]}}
>  class to help us find location of various jars. The implementation is very 
> buggy as it depends on jar name and default Class Loader. We already do have 
> facility in 
> {{[ClassUtils|https://github.com/apache/sqoop/blob/sqoop2/common/src/main/java/org/apache/sqoop/utils/ClassUtils.java#L132]}}
>  that is able to get location of jar given class name and we should take 
> advantage of that instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to