[
https://issues.apache.org/jira/browse/SQOOP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105573#comment-13105573
]
Hudson commented on SQOOP-325:
------------------------------
Integrated in Sqoop-jdk-1.6 #24 (See
[https://builds.apache.org/job/Sqoop-jdk-1.6/24/])
SQOOP-325. Sqoop doesn't build on itelliJ.
(Alex Newman via Arvind Prabhakar)
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1171193
Files :
* /incubator/sqoop/trunk/ivy/libraries.properties
* /incubator/sqoop/trunk/pom.xml
> Sqoop doesn't build on intellij
> -------------------------------
>
> Key: SQOOP-325
> URL: https://issues.apache.org/jira/browse/SQOOP-325
> Project: Sqoop
> Issue Type: Bug
> Reporter: Alex Newman
> Assignee: Alex Newman
> Priority: Minor
> Attachments: 0001-SQOOP-325.-Sqoop-doesn-t-build-on-intellij.patch,
> 0001-SQOOP-325.-Sqoop-doesn-t-build-on-intellij.patch,
> 0001-SQOOP-325.-Sqoop-doesn-t-build-on-intellij.patch
>
>
> By default, since log4j is explicitly excluded in the pom.xml. Intellij wont
> be able to build sqoop in the places that org.apache.log4j is referenced.
> There are two options as I see it:
> Option 1: Remove the exclusion and be tied to the implicit version that the
> rest of the apache projects use
> Option 2: Explicitly import it
> Amusingly, I think the first will cause less compatibility issues, although
> it is slightly more magical.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
