[
https://issues.apache.org/jira/browse/SQOOP-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535826#comment-13535826
]
Guido Serra aka Zeph edited comment on SQOOP-526 at 12/19/12 9:51 AM:
----------------------------------------------------------------------
ookkkkkk... the pom file ended up into the "compile.classpath" too
... cause the ivy generated classpath is there too
({code}${name}.hadoop.classpath{code})
I guess I have no choice than to look into ivy and fix it...
{code:xml}
<!-- The classpath for compiling and running Sqoop -->
<if>
<isset property="hadoop.home" />
<then>
<path id="compile.classpath">
<pathelement location="${build.classes}"/>
<path refid="lib.path"/>
<fileset dir="${hadoop.home}">
<include name="hadoop-core-*.jar" />
<include name="hadoop-*-core.jar" />
<include name="hadoop-common-*.jar" />
<include name="hadoop-mapred-*.jar" />
<include name="hadoop-hdfs-*.jar" />
</fileset>
<fileset dir="${hadoop.home}/lib">
<include name="*.jar" />
</fileset>
<path refid="${name}.hadoop.classpath"/>
</path>
</then>
<else>
<path id="compile.classpath">
<pathelement location="${build.classes}"/>
<path refid="lib.path"/>
<path refid="${name}.hadoop.classpath"/>
</path>
</else>
</if>
{code}
was (Author: zeph):
ookkkkkk... the pom file ended up into the "compile.classpath" too
... cause the ivy generated classpath is there too
({code}${name}.hadoop.classpath{code})
I guess I have no choice than to look into ivy and fix it...
{code:xml}
<!-- The classpath for compiling and running Sqoop -->
<if>
<isset property="hadoop.home" />
<then>
<path id="compile.classpath">
<pathelement location="${build.classes}"/>
<path refid="lib.path"/>
<fileset dir="${hadoop.home}">
<include name="hadoop-core-*.jar" />
<include name="hadoop-*-core.jar" />
<include name="hadoop-common-*.jar" />
<include name="hadoop-mapred-*.jar" />
<include name="hadoop-hdfs-*.jar" />
</fileset>
<fileset dir="${hadoop.home}/lib">
<include name="*.jar" />
</fileset>
<path refid="${name}.hadoop.classpath"/>
</path>
</then>
<else>
<path id="compile.classpath">
<pathelement location="${build.classes}"/>
<path refid="lib.path"/>
<path refid="${name}.hadoop.classpath"/>
</path>
</else>
</if>
{code:xml}
> Unable to resolve maven-scm-providers-standard
> ----------------------------------------------
>
> Key: SQOOP-526
> URL: https://issues.apache.org/jira/browse/SQOOP-526
> Project: Sqoop
> Issue Type: Bug
> Components: build
> Affects Versions: 1.4.1-incubating, 1.4.2, 1.4.3
> Environment: ubuntu 11
> Reporter: Rajesh Koilpillai
> Assignee: Guido Serra aka Zeph
> Priority: Trivial
> Attachments: remove_pom.diff
>
>
> Not sure why it is unable to resolve this POM while running "ant test", tried
> removing the folder and re-tried but it didn't seem to make any difference.
> Unable to obtain resource from
> /home/rajesh/.ivy2/cache/org.apache.maven.scm/maven-scm-providers-standard/poms/maven-scm-providers-standard-1.6.pom:
> java.util.zip.ZipException: error in opening zip file
> [junit] Unable to obtain resource from
> /home/rajesh/.ivy2/cache/org.apache.maven.scm/maven-scm-providers-standard/poms/maven-scm-providers-standard-1.6.pom:
>
> [junit] java.util.zip.ZipException: error in opening zip file
> [junit] at java.util.zip.ZipFile.open(Native Method)
> [junit] at java.util.zip.ZipFile.<init>(ZipFile.java:127)
> [junit] at java.util.jar.JarFile.<init>(JarFile.java:135)
> [junit] at java.util.jar.JarFile.<init>(JarFile.java:99)
> [junit] at
> org.apache.tools.ant.AntClassLoader.getResourceURL(AntClassLoader.java:1002)
> [junit] at
> org.apache.tools.ant.AntClassLoader$ResourceEnumeration.findNextResource(AntClassLoader.java:145)
> [junit] at
> org.apache.tools.ant.AntClassLoader$ResourceEnumeration.<init>(AntClassLoader.java:109)
> [junit] at
> org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:949)
> [junit] at
> org.apache.tools.ant.AntClassLoader.getNamedResources(AntClassLoader.java:918)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
