Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-526

Unable to resolve maven-scm-providers-standard

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 1.4.1-incubating, 1.4.2, 1.4.3
    • Fix Version/s: 1.4.3
    • Component/s: build
    • Labels:
      None
    • Environment:

      ubuntu 11

      Description

      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)

      1. ivy_pom.diff
        0.8 kB
        Guido Serra aka Zeph
      2. pom.patch
        0.3 kB
        Guido Serra aka Zeph
      3. remove_pom.diff
        1 kB
        Guido Serra aka Zeph

        Issue Links

          Activity

          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          I've tried to investigate this and it appears to me that the code is trying to work with pom file as it was jar (it's trying to open zip file to get the resources). I was not able to find precise piece of code to fix this.

          However I believe that it's not a blocker for upcoming 1.4.2 release.

          Jarcec

          Show
          jarcec Jarek Jarcec Cecho added a comment - I've tried to investigate this and it appears to me that the code is trying to work with pom file as it was jar (it's trying to open zip file to get the resources). I was not able to find precise piece of code to fix this. However I believe that it's not a blocker for upcoming 1.4.2 release. Jarcec
          Hide
          zeph Guido Serra aka Zeph added a comment - - edited

          it seems related to the way junit is getting instrumented:

          I'm looking into this section of the build.xml on how to change it to avoid this

          ...
          
                <classpath>
                  <!-- instrumented classes go ahead of normal classes -->
                  <pathelement location="${cobertura.class.dir}" />
          
                  <!-- main classpath here. -->
                  <path refid="test.classpath" />
          
                  <!-- need thirdparty JDBC drivers for thirdparty tests -->
                  <fileset dir="${sqoop.thirdparty.lib.dir}"
                      includes="*.jar" />
          
                  <!-- include cobertura itself on the classpath -->
                  <path refid="cobertura.classpath" />
                </classpath>
                <formatter type="${test.junit.output.format}" />
                <batchtest todir="${build.test}" unless="testcase">
                  <fileset dir="${test.dir}"
                           includes="**/${test.pattern}.java"
                           excludes="**/${test.exclude}.java" />
                </batchtest>
                <batchtest todir="${build.test}" if="testcase">
                  <fileset dir="${test.dir}" includes="**/${testcase}.java"/>
                </batchtest>
              </junit>
            </target>
          

          ref: http://cobertura.sourceforge.net/anttaskreference.html

          Show
          zeph Guido Serra aka Zeph added a comment - - edited it seems related to the way junit is getting instrumented: http://stackoverflow.com/questions/461417/configuring-ant-to-run-unit-tests-where-should-libraries-be-how-should-classpa http://stackoverflow.com/questions/6015092/zipexception-when-running-junit-tests http://stackoverflow.com/questions/8655193/not-able-to-run-test-through-ant I'm looking into this section of the build.xml on how to change it to avoid this ... <classpath> <!-- instrumented classes go ahead of normal classes --> <pathelement location= "${cobertura.class.dir}" /> <!-- main classpath here. --> <path refid= "test.classpath" /> <!-- need thirdparty JDBC drivers for thirdparty tests --> <fileset dir= "${sqoop.thirdparty.lib.dir}" includes= "*.jar" /> <!-- include cobertura itself on the classpath --> <path refid= "cobertura.classpath" /> </classpath> <formatter type= "${test.junit.output.format}" /> <batchtest todir= "${build.test}" unless= "testcase" > <fileset dir= "${test.dir}" includes= "**/${test.pattern}.java" excludes= "**/${test.exclude}.java" /> </batchtest> <batchtest todir= "${build.test}" if= "testcase" > <fileset dir= "${test.dir}" includes= "**/${testcase}.java" /> </batchtest> </junit> </target> ref: http://cobertura.sourceforge.net/anttaskreference.html
          Hide
          zeph Guido Serra aka Zeph added a comment -

          k, definitely related to how Cobertura gets the classpath, if non .jar files are present (.txt .class .java)

          Show
          zeph Guido Serra aka Zeph added a comment - k, definitely related to how Cobertura gets the classpath, if non .jar files are present (.txt .class .java) http://jira.grails.org/browse/GPCODECOVERAGE-46
          Hide
          zeph Guido Serra aka Zeph added a comment - - edited

          k, it looks like the .pom file ended up in the classpath...

          ...
              </junit>
                <echo>WHATEVER! ${cobertura.class.dir}</echo>
                <echo>WHATEVER! ${ant.refid:test.classpath}</echo>
                <echo>WHATEVER! ${sqoop.thirdparty.lib.dir}</echo>
                <echo>WHATEVER! ${ant.refid:cobertura.classpath}</echo>
          
          v1:sqoop zeph$ grep WHATEVER execution.log |grep -v jar
               [echo] WHATEVER! /Users/zeph/tmp/sqoop/build/cobertura/classes
               [echo] WHATEVER! 
               [echo] WHATEVER! 
          v1:sqoop zeph$ rm execution.log 
          v1:sqoop zeph$ grep -v '.jar$' oneline.log 
               [echo] WHATEVER! /Users/zeph/tmp/sqoop/build/test/classes
          /Users/zeph/.ivy2/cache/org.apache.maven.scm/maven-scm-providers-standard/poms/maven-scm-providers-standard-1.6.pom
          /Users/zeph/tmp/sqoop/build/classes
          

          within...

          ${ant.refid:test.classpath}

          created at:

              <!-- Classpath for unit tests (superset of compile.classpath) -->
              <path id="test.classpath">
                <pathelement location="${build.test.classes}" />
                <path refid="${name}.hadooptest.classpath" />
                <path refid="compile.classpath" />
              </path>
          

          in the "init" task...

          Show
          zeph Guido Serra aka Zeph added a comment - - edited k, it looks like the .pom file ended up in the classpath... ... </junit> <echo> WHATEVER! ${cobertura.class.dir} </echo> <echo> WHATEVER! ${ant.refid:test.classpath} </echo> <echo> WHATEVER! ${sqoop.thirdparty.lib.dir} </echo> <echo> WHATEVER! ${ant.refid:cobertura.classpath} </echo> v1:sqoop zeph$ grep WHATEVER execution.log |grep -v jar [echo] WHATEVER! /Users/zeph/tmp/sqoop/build/cobertura/classes [echo] WHATEVER! [echo] WHATEVER! v1:sqoop zeph$ rm execution.log v1:sqoop zeph$ grep -v '.jar$' oneline.log [echo] WHATEVER! /Users/zeph/tmp/sqoop/build/test/classes /Users/zeph/.ivy2/cache/org.apache.maven.scm/maven-scm-providers-standard/poms/maven-scm-providers-standard-1.6.pom /Users/zeph/tmp/sqoop/build/classes within... ${ant.refid:test.classpath} created at: <!-- Classpath for unit tests (superset of compile.classpath) --> <path id= "test.classpath" > <pathelement location= "${build.test.classes}" /> <path refid= "${name}.hadooptest.classpath" /> <path refid= "compile.classpath" /> </path> in the "init" task...
          Hide
          zeph Guido Serra aka Zeph added a comment -

          constructed by ivy...

            <target name="ivy-retrieve-hadoop" depends="ivy-init,ivy-resolve-hadoop">
              <!-- retrieve hadoop refs normally. -->
              <ivy:retrieve settingsRef="${name}.ivy.settings"
                 pattern="${build.ivy.lib.dir}/${ivy.artifact.retrieve.pattern}"
                 sync="true" />
              <ivy:cachepath pathid="${name}.hadoop.classpath" conf="hadoop${hadoopversion}" />
              <echo>WHATEVER!!! ${ant.refid:sqoop.hadoop.classpath}</echo>
            </target>
          
          Show
          zeph Guido Serra aka Zeph added a comment - constructed by ivy... <target name= "ivy-retrieve-hadoop" depends= "ivy-init,ivy-resolve-hadoop" > <!-- retrieve hadoop refs normally. --> <ivy:retrieve settingsRef= "${name}.ivy.settings" pattern= "${build.ivy.lib.dir}/${ivy.artifact.retrieve.pattern}" sync= "true" /> <ivy:cachepath pathid= "${name}.hadoop.classpath" conf= "hadoop${hadoopversion}" /> <echo> WHATEVER!!! ${ant.refid:sqoop.hadoop.classpath} </echo> </target>
          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          Hi Guido,
          thank you very much for diving into this issue, I appreciate your time and effort. You seems pretty much on top of this JIRA, so please feel free to submit a patch, I'll be more than happy to review it!

          I've added you to "contributor" list on JIRA, so you can self assign this ticket to you now.

          Jarcec

          Show
          jarcec Jarek Jarcec Cecho added a comment - Hi Guido, thank you very much for diving into this issue, I appreciate your time and effort. You seems pretty much on top of this JIRA, so please feel free to submit a patch, I'll be more than happy to review it! I've added you to "contributor" list on JIRA, so you can self assign this ticket to you now. Jarcec
          Hide
          zeph Guido Serra aka Zeph added a comment -

          patch created!

          • remove_pom.diff
          Show
          zeph Guido Serra aka Zeph added a comment - patch created! remove_pom.diff
          Hide
          zeph Guido Serra aka Zeph added a comment -

          basically I had to cleanup the classpath from the .pom file that got included by ivy

          Show
          zeph Guido Serra aka Zeph added a comment - basically I had to cleanup the classpath from the .pom file that got included by ivy
          Hide
          zeph Guido Serra aka Zeph added a comment -

          oh, tnx Jarek Jarcec Cecho! ...I saw now ur comment. Anyway, now it is fixed (probably not elegant, but I don't know the downside of altering ivy, so I preferred to clean up at ant level)

          Show
          zeph Guido Serra aka Zeph added a comment - oh, tnx Jarek Jarcec Cecho ! ...I saw now ur comment. Anyway, now it is fixed (probably not elegant, but I don't know the downside of altering ivy, so I preferred to clean up at ant level)
          Hide
          zeph Guido Serra aka Zeph added a comment - - edited

          k... applying the patch, all tests start to fail... no good

          back to coding...

          test-core:
             [delete] Deleting directory /Users/zeph/tmp/sqoop/build/test/logs
              [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/logs
             [delete] Deleting directory /Users/zeph/tmp/sqoop/build/test/data
              [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/data
              [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/cobertura/classes
              [junit] Running com.cloudera.sqoop.TestAllTables
              [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
              [junit] Test com.cloudera.sqoop.TestAllTables FAILED
              [junit] Running com.cloudera.sqoop.TestAppendUtils
              [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
              [junit] Test com.cloudera.sqoop.TestAppendUtils FAILED
          ...
          

          got it, I stripped the test classes too

          v1:sqoop zeph$ diff xa*
          1c1
          <      [echo] WITH .pom!!! 
          ---
          >      [echo] WITHOUT .pom!!! 
          94d93
          < /Users/zeph/.ivy2/cache/org.apache.maven.scm/maven-scm-providers-standard/poms/maven-scm-providers-standard-1.6.pom
          158,159d156
          < /Users/zeph/tmp/sqoop/build/classes
          < /Users/zeph/tmp/sqoop/build/test/classes
          
          Show
          zeph Guido Serra aka Zeph added a comment - - edited k... applying the patch, all tests start to fail... no good back to coding... test-core: [delete] Deleting directory /Users/zeph/tmp/sqoop/build/test/logs [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/logs [delete] Deleting directory /Users/zeph/tmp/sqoop/build/test/data [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/data [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/cobertura/classes [junit] Running com.cloudera.sqoop.TestAllTables [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Test com.cloudera.sqoop.TestAllTables FAILED [junit] Running com.cloudera.sqoop.TestAppendUtils [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Test com.cloudera.sqoop.TestAppendUtils FAILED ... got it, I stripped the test classes too v1:sqoop zeph$ diff xa* 1c1 < [echo] WITH .pom!!! --- > [echo] WITHOUT .pom!!! 94d93 < /Users/zeph/.ivy2/cache/org.apache.maven.scm/maven-scm-providers-standard/poms/maven-scm-providers-standard-1.6.pom 158,159d156 < /Users/zeph/tmp/sqoop/build/classes < /Users/zeph/tmp/sqoop/build/test/classes
          Hide
          zeph Guido Serra aka Zeph added a comment - - edited

          ookkkkkk... the pom file ended up into the "compile.classpath" too
          ... cause the ivy generated classpath is there too

          ${name}.hadoop.classpath

          I guess I have no choice than to look into ivy and fix it...

            <!-- 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>
          
          Show
          zeph Guido Serra aka Zeph added a comment - - edited ookkkkkk... the pom file ended up into the "compile.classpath" too ... cause the ivy generated classpath is there too ${name}.hadoop.classpath I guess I have no choice than to look into ivy and fix it... <!-- 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>
          Hide
          zeph Guido Serra aka Zeph added a comment -

          k, fixed...

          run-tests:
               [echo] Use Hadoop 23
               [echo] Use org.apache.sqoop.manager.DefaultManagerFactory
          
          test-core:
              [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/logs
              [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/data
              [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/cobertura/classes
              [junit] Running com.cloudera.sqoop.TestAllTables
              [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.878 sec
              [junit] Running com.cloudera.sqoop.TestAppendUtils
              [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 10.528 sec
          

          this was it...

          ^Cv1:sqoop zeph$ git diff
          diff --git a/build.xml b/build.xml
          index 9c400ea..651c044 100644
          --- a/build.xml
          +++ b/build.xml
          @@ -657,6 +657,8 @@
               <delete dir="${build.test}/data"/>
               <mkdir dir="${build.test}/data" />
               <mkdir dir="${cobertura.class.dir}" />
          +    <!--  https://issues.apache.org/jira/browse/SQOOP-526
          +        <echo>WITH(OUT)!!! ${ant.refid:test.classpath}</echo> -->
               <junit
                 printsummary="yes" showoutput="${test.output}"
                 haltonfailure="no" fork="yes" maxmemory="512m"
          diff --git a/ivy.xml b/ivy.xml
          index ca2b89b..1ee60df 100644
          --- a/ivy.xml
          +++ b/ivy.xml
          @@ -169,6 +169,7 @@ under the License.
           
               <exclude org="org.apache.hadoop" module="avro"/>
               <exclude org="commons-daemon" module="commons-daemon" />
          +    <exclude type="pom" />
           
             </dependencies>
           </ivy-module>
          
          Show
          zeph Guido Serra aka Zeph added a comment - k, fixed... run-tests: [echo] Use Hadoop 23 [echo] Use org.apache.sqoop.manager.DefaultManagerFactory test-core: [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/logs [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/test/data [mkdir] Created dir: /Users/zeph/tmp/sqoop/build/cobertura/classes [junit] Running com.cloudera.sqoop.TestAllTables [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.878 sec [junit] Running com.cloudera.sqoop.TestAppendUtils [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 10.528 sec this was it... ^Cv1:sqoop zeph$ git diff diff --git a/build.xml b/build.xml index 9c400ea..651c044 100644 --- a/build.xml +++ b/build.xml @@ -657,6 +657,8 @@ <delete dir= "${build.test}/data" /> <mkdir dir= "${build.test}/data" /> <mkdir dir= "${cobertura.class.dir}" /> + <!-- https: //issues.apache.org/jira/browse/SQOOP-526 + <echo>WITH(OUT)!!! ${ant.refid:test.classpath}</echo> --> <junit printsummary= "yes" showoutput= "${test.output}" haltonfailure= "no" fork= "yes" maxmemory= "512m" diff --git a/ivy.xml b/ivy.xml index ca2b89b..1ee60df 100644 --- a/ivy.xml +++ b/ivy.xml @@ -169,6 +169,7 @@ under the License. <exclude org= "org.apache.hadoop" module= "avro" /> <exclude org= "commons-daemon" module= "commons-daemon" /> + <exclude type= "pom" /> </dependencies> </ivy-module>
          Hide
          zeph Guido Serra aka Zeph added a comment -
          • ivy_pom.diff
          Show
          zeph Guido Serra aka Zeph added a comment - ivy_pom.diff
          Hide
          zeph Guido Serra aka Zeph added a comment -

          Jarek Jarcec Cecho done properly, who can apply this now? (and maybe have a double check of it)

          Show
          zeph Guido Serra aka Zeph added a comment - Jarek Jarcec Cecho done properly, who can apply this now? (and maybe have a double check of it)
          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          Hi Guido,
          one of the committers needs to take a look and commit it. Unfortunately I'm traveling around Christmas, so I don't have much time to spare myself right now, but I'll try to take a look soon. Don't worry, your contribution won't be forgotten

          Jarcec

          Show
          jarcec Jarek Jarcec Cecho added a comment - Hi Guido, one of the committers needs to take a look and commit it. Unfortunately I'm traveling around Christmas, so I don't have much time to spare myself right now, but I'll try to take a look soon. Don't worry, your contribution won't be forgotten Jarcec
          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          Hi Guido,
          thank you very much for diving into this issue. I've took a look on most recent patch "ivy_pom.xml" and I can confirm that applying it, the weird error message goes away. I've noticed that you are also changing build.xml file by adding comment. It seems to me that the comment is artifact from your previous testing. Do you think that it would make sense to remove it?

          Jarcec

          Show
          jarcec Jarek Jarcec Cecho added a comment - Hi Guido, thank you very much for diving into this issue. I've took a look on most recent patch "ivy_pom.xml" and I can confirm that applying it, the weird error message goes away. I've noticed that you are also changing build.xml file by adding comment. It seems to me that the comment is artifact from your previous testing. Do you think that it would make sense to remove it? Jarcec
          Hide
          zeph Guido Serra aka Zeph added a comment -

          It is just a comment and it keeps a reference to the issue. Up to you. I usually prefer to be verbose so other people have that information at hand...

          Show
          zeph Guido Serra aka Zeph added a comment - It is just a comment and it keeps a reference to the issue. Up to you. I usually prefer to be verbose so other people have that information at hand...
          Hide
          venkatnrangan Venkat Ranganathan added a comment -

          Good work on fixing this issue. I think this should also fix the eclipse project generation where the generated project has this one jar in the buildpath treated as a zip file. (If you look at the problem view of a generated SQOOP eclipse project, you will see an error for this)

          Show
          venkatnrangan Venkat Ranganathan added a comment - Good work on fixing this issue. I think this should also fix the eclipse project generation where the generated project has this one jar in the buildpath treated as a zip file. (If you look at the problem view of a generated SQOOP eclipse project, you will see an error for this)
          Hide
          zeph Guido Serra aka Zeph added a comment - - edited

          tnx [~nrv]

          p.s. it would have been fine if it would have been a jar file...
          since a jar is a zip file... instead it was a pom file, which is pure xml

          Show
          zeph Guido Serra aka Zeph added a comment - - edited tnx [~nrv] p.s. it would have been fine if it would have been a jar file... since a jar is a zip file... instead it was a pom file, which is pure xml
          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          Hi Guido,
          I generally agree that comments are good thing to keep the reference. However this particular one seems weird. I would prefer to remove it before committing.

          Jarcec

          Show
          jarcec Jarek Jarcec Cecho added a comment - Hi Guido, I generally agree that comments are good thing to keep the reference. However this particular one seems weird. I would prefer to remove it before committing. Jarcec
          Hide
          zeph Guido Serra aka Zeph added a comment -

          as said, ur decision... fine by me

          Show
          zeph Guido Serra aka Zeph added a comment - as said, ur decision... fine by me
          Hide
          venkatnrangan Venkat Ranganathan added a comment -

          Guido Serra aka Zeph Sorry I meant non-jar .pom file in the build path. I did verify that the eclipse issue is gone. I will create another JIRA and mark it as duplicate of this for the eclipse issue so that people searching for eclipse solution also can get to the solution

          Show
          venkatnrangan Venkat Ranganathan added a comment - Guido Serra aka Zeph Sorry I meant non-jar .pom file in the build path. I did verify that the eclipse issue is gone. I will create another JIRA and mark it as duplicate of this for the eclipse issue so that people searching for eclipse solution also can get to the solution
          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          Guido,
          would you mind removing the comment from your previous patch and attaching new version, so that I can commit it in?

          Jarcec

          Show
          jarcec Jarek Jarcec Cecho added a comment - Guido, would you mind removing the comment from your previous patch and attaching new version, so that I can commit it in? Jarcec
          Hide
          zeph Guido Serra aka Zeph added a comment -
          • pom.patch

          here u go

          Show
          zeph Guido Serra aka Zeph added a comment - pom.patch here u go
          Hide
          jarcec Jarek Jarcec Cecho added a comment -

          This patch is quite simple, so I'm giving my +1 here.

          Show
          jarcec Jarek Jarcec Cecho added a comment - This patch is quite simple, so I'm giving my +1 here.
          Hide
          jarcec Jarek Jarcec Cecho added a comment -
          Show
          jarcec Jarek Jarcec Cecho added a comment - The patch is in: https://git-wip-us.apache.org/repos/asf?p=sqoop.git;a=commit;h=b79c4b9e85e21d041cc9bc0b16d2f87456775224 Thank you Guide for your contribution! Jarcec
          Hide
          zeph Guido Serra aka Zeph added a comment -

          u welcome

          Show
          zeph Guido Serra aka Zeph added a comment - u welcome
          Hide
          hudson Hudson added a comment -

          Integrated in Sqoop-ant-jdk-1.6-hadoop200 #390 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/390/)
          SQOOP-526: Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224)

          Result = SUCCESS
          jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224
          Files :

          • ivy.xml
          Show
          hudson Hudson added a comment - Integrated in Sqoop-ant-jdk-1.6-hadoop200 #390 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/390/ ) SQOOP-526 : Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224) Result = SUCCESS jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224 Files : ivy.xml
          Hide
          hudson Hudson added a comment -

          Integrated in Sqoop-ant-jdk-1.6-hadoop100 #400 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop100/400/)
          SQOOP-526: Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224)

          Result = SUCCESS
          jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224
          Files :

          • ivy.xml
          Show
          hudson Hudson added a comment - Integrated in Sqoop-ant-jdk-1.6-hadoop100 #400 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop100/400/ ) SQOOP-526 : Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224) Result = SUCCESS jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224 Files : ivy.xml
          Hide
          hudson Hudson added a comment -

          Integrated in Sqoop-ant-jdk-1.6-hadoop20 #402 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop20/402/)
          SQOOP-526: Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224)

          Result = SUCCESS
          jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224
          Files :

          • ivy.xml
          Show
          hudson Hudson added a comment - Integrated in Sqoop-ant-jdk-1.6-hadoop20 #402 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop20/402/ ) SQOOP-526 : Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224) Result = SUCCESS jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224 Files : ivy.xml
          Hide
          hudson Hudson added a comment -

          Integrated in Sqoop-ant-jdk-1.6-hadoop23 #594 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop23/594/)
          SQOOP-526: Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224)

          Result = SUCCESS
          jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224
          Files :

          • ivy.xml
          Show
          hudson Hudson added a comment - Integrated in Sqoop-ant-jdk-1.6-hadoop23 #594 (See https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop23/594/ ) SQOOP-526 : Unable to resolve maven-scm-providers-standard (Revision b79c4b9e85e21d041cc9bc0b16d2f87456775224) Result = SUCCESS jarcec : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b79c4b9e85e21d041cc9bc0b16d2f87456775224 Files : ivy.xml

            People

            • Assignee:
              zeph Guido Serra aka Zeph
              Reporter:
              rajeshkoil Rajesh Koilpillai
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development