[
https://issues.apache.org/jira/browse/MAPREDUCE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791141#action_12791141
]
Aaron Kimball commented on MAPREDUCE-1146:
------------------------------------------
I don't follow -- this isn't related to "Eclipse arcana." The requirements
imposed by Eclipse are straightforward: we need to create a classpath file
containing a list of exactly the jars necessary to compile the project. We are
currently doing this via a template file and some substitutions executed by our
ant buildfile. To my knowledge, this is the state of the art. The file format
is XML and the schema is straightforward.
Since Sqoop requires a certain jar found in a user-defined location, only on
certain platforms, I implemented conditional logic in our buildfile to check
the platform, and inject the correct jar dependency into the Eclipse project
classpath file if it's being constructed in a platform which requires this jar.
When you canceled the patch, it seemed to be because you didn't like the degree
of complexity I placed in the ant script. If you have a simpler solution, I'm
receptive, but I don't think there's a less-complicated way (given the
constraints imposed by our build system of choice, ant) to implement this,
short of using ant to invoke a bash script. But I think that adds its own
subtleties and complexities that make that an even less-attractive choice.
> Sqoop dependencies break Ecpilse build on Linux
> -----------------------------------------------
>
> Key: MAPREDUCE-1146
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1146
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/sqoop
> Environment: Linux, Sun JDK6
> Reporter: Konstantin Boudnik
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1146.2.patch, MAPREDUCE-1146.3.patch,
> MAPREDUCE-1146.patch
>
>
> Under Linux there's the error in the Eclipse "Problems" view:
> {noformat}
> - "com.sun.tools cannot be resolved" at line 166 of
> org.apache.hadoop.sqoop.orm.CompilationManager
> {noformat}
> The problem doesn't appear on MacOS though
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
