[
https://issues.apache.org/jira/browse/SQOOP-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091985#comment-14091985
]
Jarek Jarcec Cecho commented on SQOOP-1424:
-------------------------------------------
Thank you for taking a look [~abec]! I'm actually following the common best
practice with multi-module maven project. The root {{pom.xml}} contains the
guava definition including version in {{dependencyManagement}} section, whereas
each module that actually needs it will declare the dependency in it's
{{pom.xml}} in {{dependencies}} section, but without specifying version. This
way, all the project dependencies are nicely visible in the root {{pom.xml}}
and are easier to maintain as all versions are defined there as well. Take a
look into [maven
docs|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management]
for more details.
> Sqoop2: Simply SqoopCommand in shell package
> --------------------------------------------
>
> Key: SQOOP-1424
> URL: https://issues.apache.org/jira/browse/SQOOP-1424
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.3
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.4
>
> Attachments: SQOOP-1424.patch
>
>
> I've noticed that the {{SqoopCommand}} implementations are copy&pasting a lot
> of code. Would be great to simplify all that.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
