Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-1838

Pig build does not publish artifacts of build

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.1.0
    • Component/s: None
    • Labels:
      None

      Description

      The pig build does not execute the mvn-install target. This means that other pieces of the bigtop ecosystem do not pick up the correct pig dependencies from the bigtop build. Instead, they pick them up from the central maven repository (or they fail to find them if a bigtop has pig version that is not publicly released).

      This is a problem because builds like datafu pick up their pig dependency via ivy and they are not able to do so.

        Issue Links

          Activity

          Hide
          cos Konstantin Boudnik added a comment -

          Committed and pushed to the master. Thanks Rob!

          Show
          cos Konstantin Boudnik added a comment - Committed and pushed to the master. Thanks Rob!
          Hide
          rleidle Rob Leidle added a comment -

          Yes (all targets are copies):

          <target name="maven-artifacts" depends="copy-jar-to-maven, copypom" />

          <target name="published" depends="ivy-publish-local, maven-artifacts"/>

          Show
          rleidle Rob Leidle added a comment - Yes (all targets are copies): <target name="maven-artifacts" depends="copy-jar-to-maven, copypom" /> <target name="published" depends="ivy-publish-local, maven-artifacts"/>
          Hide
          cos Konstantin Boudnik added a comment -

          Don't remember all the details about the Pig build but just to make sure: published doesn't try to deploy the artifacts to the remote repo or something? Just local deployment, right? If so +1 and I will commit it once I hear your reply to my comment above. Thanks!

          Show
          cos Konstantin Boudnik added a comment - Don't remember all the details about the Pig build but just to make sure: published doesn't try to deploy the artifacts to the remote repo or something? Just local deployment, right? If so +1 and I will commit it once I hear your reply to my comment above. Thanks!
          Hide
          rleidle Rob Leidle added a comment -

          patch added.

          Show
          rleidle Rob Leidle added a comment - patch added.
          Hide
          cos Konstantin Boudnik added a comment -

          I think you can take a look at 0.8 branch, 0.7 would be the latest.

          Show
          cos Konstantin Boudnik added a comment - I think you can take a look at 0.8 branch, 0.7 would be the latest.
          Hide
          rleidle Rob Leidle added a comment -

          OH thanks, that would be helpful to see an example. I guess it would be in an older bigtop since Hive is maven now.

          Show
          rleidle Rob Leidle added a comment - OH thanks, that would be helpful to see an example. I guess it would be in an older bigtop since Hive is maven now.
          Hide
          cos Konstantin Boudnik added a comment - - edited

          I think we have/had a similar problem with Hive IIRC. We had to do some sed majic in the do-component-build to replace a remote Ivy resolver w/ local one or something of the sort. I bet you should be able to add a local Ivy resolver for DataFu build as well, e.g. to use local Maven ~/.m2

          Show
          cos Konstantin Boudnik added a comment - - edited I think we have/had a similar problem with Hive IIRC. We had to do some sed majic in the do-component-build to replace a remote Ivy resolver w/ local one or something of the sort. I bet you should be able to add a local Ivy resolver for DataFu build as well, e.g. to use local Maven ~/.m2
          Hide
          rleidle Rob Leidle added a comment -

          Hey Kons, problem is i don't have a solution yet for datafu – it isn't ready it's ivy dependencies out of the local repository. I changed the pig build to execute the "published" target which publishes to the local maven and ivy. However, datafu's ivy is not setup to read dependencies out of local. Would be good if the datafu expert or an ivy expert could help out with some input here.

          Show
          rleidle Rob Leidle added a comment - Hey Kons, problem is i don't have a solution yet for datafu – it isn't ready it's ivy dependencies out of the local repository. I changed the pig build to execute the "published" target which publishes to the local maven and ivy. However, datafu's ivy is not setup to read dependencies out of local. Would be good if the datafu expert or an ivy expert could help out with some input here.
          Hide
          cos Konstantin Boudnik added a comment -

          If that's not too much trouble - perhaps we can assign it against 1.0? The RC still isn't ready yet ;(

          Show
          cos Konstantin Boudnik added a comment - If that's not too much trouble - perhaps we can assign it against 1.0? The RC still isn't ready yet ;(

            People

            • Assignee:
              cos Konstantin Boudnik
              Reporter:
              rleidle Rob Leidle
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development