Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.0.0
    • Component/s: build
    • Labels:
      None

      Description

      Pig build fails with

      [ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
      [ivy:resolve] 		::              FAILED DOWNLOADS            ::
      [ivy:resolve] 		:: ^ see resolution messages for details  ^ ::
      [ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
      [ivy:resolve] 		:: org.mortbay.jetty#jetty;6.1.26!jetty.zip
      [ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
      

        Activity

        Hide
        plinnell Peter Linnell added a comment -

        +1 I saw the same build failure. Thanks for tracking this down.

        Show
        plinnell Peter Linnell added a comment - +1 I saw the same build failure. Thanks for tracking this down.
        Hide
        apurtell Andrew Purtell added a comment -

        We need this in 0.8 too, it's a blocker for the RC

        Show
        apurtell Andrew Purtell added a comment - We need this in 0.8 too, it's a blocker for the RC
        Hide
        cos Konstantin Boudnik added a comment -

        I don't see why this is a blocker, as there's a work-around, but I won't argue too strongly.

        Show
        cos Konstantin Boudnik added a comment - I don't see why this is a blocker, as there's a work-around, but I won't argue too strongly.
        Hide
        apurtell Andrew Purtell added a comment -

        I think its a blocker because someone trying to build the whole stack with Bigtop will see a failed build at this step instead of a successful outcome.

        Show
        apurtell Andrew Purtell added a comment - I think its a blocker because someone trying to build the whole stack with Bigtop will see a failed build at this step instead of a successful outcome.
        Hide
        cos Konstantin Boudnik added a comment -

        Yes, but the solution is to just remove the artifact from both ivy-cache and m2 directories. As it doesn't block the further progress of the build - I don't think it is a blocker. Again - I am ok with getting this in if we end up fixing other issues - e.g. the one with Mahout. Otherwise, it doesn't worth a respin from my standpoint - especially considering that our CI is screwed up and the next build might take anywhere from a week to a month to get done.

        Show
        cos Konstantin Boudnik added a comment - Yes, but the solution is to just remove the artifact from both ivy-cache and m2 directories. As it doesn't block the further progress of the build - I don't think it is a blocker. Again - I am ok with getting this in if we end up fixing other issues - e.g. the one with Mahout. Otherwise, it doesn't worth a respin from my standpoint - especially considering that our CI is screwed up and the next build might take anywhere from a week to a month to get done.
        Hide
        apurtell Andrew Purtell added a comment -

        I have first deleted all of .ant .ivy2 and .m2 and the build fails due to this issue. Are you saying a user can then remove .ivy2 and .m2 again?

        Show
        apurtell Andrew Purtell added a comment - I have first deleted all of .ant .ivy2 and .m2 and the build fails due to this issue. Are you saying a user can then remove .ivy2 and .m2 again?
        Hide
        cos Konstantin Boudnik added a comment - - edited

        it means that the proposed patch doesn't work. Roman Shaposhnik- any comments?

        Show
        cos Konstantin Boudnik added a comment - - edited it means that the proposed patch doesn't work. Roman Shaposhnik - any comments?
        Hide
        apurtell Andrew Purtell added a comment -

        I was able to work around this by manually downloading the requisite Jetty zip into the cache. It's an ugly hack but does work if more reasonable options fail.

        Show
        apurtell Andrew Purtell added a comment - I was able to work around this by manually downloading the requisite Jetty zip into the cache. It's an ugly hack but does work if more reasonable options fail.
        Hide
        rvs Roman Shaposhnik added a comment -

        Andrew Purtell removing all caches doesn't work. you need to remove a few artifacts in the cache – and then the build passes:

        rm -rf ~/.ivy2/cache/*jetty ~/.m2/repository/org/mortbay ~/.m2/repository/org/eclipse/jetty
        
        Show
        rvs Roman Shaposhnik added a comment - Andrew Purtell removing all caches doesn't work. you need to remove a few artifacts in the cache – and then the build passes: rm -rf ~/.ivy2/cache/*jetty ~/.m2/repository/org/mortbay ~/.m2/repository/org/eclipse/jetty
        Hide
        apurtell Andrew Purtell added a comment -

        Is this a transient resolution error? I just noticed that another build I kicked off on a different network went so far as to encounter BIGTOP-1434, when the Sqoop build blows up due to an inscrutable Maven issue. This was a work box where I've never attempted a Bigtop build before.

        Show
        apurtell Andrew Purtell added a comment - Is this a transient resolution error? I just noticed that another build I kicked off on a different network went so far as to encounter BIGTOP-1434 , when the Sqoop build blows up due to an inscrutable Maven issue. This was a work box where I've never attempted a Bigtop build before.
        Hide
        apurtell Andrew Purtell added a comment -

        Maybe manually downloading this dep in particular into the cache would be better?

        Show
        apurtell Andrew Purtell added a comment - Maybe manually downloading this dep in particular into the cache would be better?
        Hide
        rvs Roman Shaposhnik added a comment -

        That is exactly what the workaround accomplishes, except the manual bit. If you remove just those artifacts, the correct ones are fetched during the build.

        The bug itself stems from buggy pom files of transitive dependencies. There's very little we (or Pig) can do to fix this.

        Show
        rvs Roman Shaposhnik added a comment - That is exactly what the workaround accomplishes, except the manual bit. If you remove just those artifacts, the correct ones are fetched during the build. The bug itself stems from buggy pom files of transitive dependencies. There's very little we (or Pig) can do to fix this.
        Hide
        apurtell Andrew Purtell added a comment -

        Could we not put a one liner into Pig's do-component-build script that invokes Maven to download the Jetty zip dep first?

        mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:get -DartifactId=jetty -DgroupId=org.mortbay.jetty -Dversion=6.1.26 -Dtype=zip
        
        Show
        apurtell Andrew Purtell added a comment - Could we not put a one liner into Pig's do-component-build script that invokes Maven to download the Jetty zip dep first? mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:get -DartifactId=jetty -DgroupId=org.mortbay.jetty -Dversion=6.1.26 -Dtype=zip
        Hide
        apurtell Andrew Purtell added a comment -

        Never mind, Maven being Maven that doesn't actually work. It won't bring down the zip packaging, and if you don't have the maven-downloader-plugin already cached the command will fail.

        Show
        apurtell Andrew Purtell added a comment - Never mind, Maven being Maven that doesn't actually work. It won't bring down the zip packaging, and if you don't have the maven-downloader-plugin already cached the command will fail.
        Hide
        rvs Roman Shaposhnik added a comment -

        I am closing it again, since it seems that we're all on the same page now.

        Andrew Purtell lemme know if you disagree

        Show
        rvs Roman Shaposhnik added a comment - I am closing it again, since it seems that we're all on the same page now. Andrew Purtell lemme know if you disagree

          People

          • Assignee:
            rvs Roman Shaposhnik
            Reporter:
            rvs Roman Shaposhnik
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development