Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-38 Mavenization (was trac #168)
  3. BLZG-1269

Converge bigdata/blazegraph core projects on version 1.5.2-SNAPSHOT (not 1.0)

    Details

      Description

      As a matter of policy, this project should have the same version number as the top-level blazegraph project and the main bigdata project (basically, I think that all central bigdata/blazegraph modules should use the same version number).

      Resolved:

      • junit-ext: declared dependency on bigdata-1.5.1. Should not have any bigdata/blazegraph dependency.

      Proposed:

      • bigdata-jini 1.0-SNAPSHOT => 1.5.2-SNAPSHOT
      • bigdata-blueprints 1.0-SNAPSHOT => 1.5.2-SNAPSHOT (note that it was using 1.0-SNAPSHOT of bigdata-client)
      • bigdata-client 1.0-SNAPSHOT => 1.5.2-SNAPSHOT
      • bigdata-ganglia 1.0-SNAPSHOT => 1.5.2-SNAPSHOT (I decided that it was easier to apply this policy to bigdata-* KISS)
      • bigdata-gas 1.0-SNAPSHOT => 1.5.2-SNAPSHOT

      Other version issues (not yet resolved)

      • dsi-utils: historical JAR version is 1.0.6. Maven release version is 1.0 but should be GTE 1.0.6.
      • lgpl-utils: historical JAR version is 1.0.7. Maven release version is 1.0 but should be GTE 1.0.7.

        Issue Links

          Activity

          Hide
          bryanthompson bryanthompson added a comment -

          Note: you can use

          <version>${bigdata.version}</version>
          

          but only after you have already resolved the parent pom. So the parent version must be explicitly given.

          Show
          bryanthompson bryanthompson added a comment - Note: you can use <version>${bigdata.version}</version> but only after you have already resolved the parent pom. So the parent version must be explicitly given.
          Hide
          bryanthompson bryanthompson added a comment -

          Converged POMs to use version info from top-level (blazegraph-parent/pom.xml).

          Converged onto zookeeper 3.4.5 since that what we are using in CI (it was 3.4.6).

          Show
          bryanthompson bryanthompson added a comment - Converged POMs to use version info from top-level (blazegraph-parent/pom.xml). Converged onto zookeeper 3.4.5 since that what we are using in CI (it was 3.4.6).
          Hide
          bryanthompson bryanthompson added a comment -

          See https://github.com/SYSTAP/bigdata/pull/69 for PR for changes per this ticket.

          We've agreed to do the following to get the snapshots published so the build should succeed without painful bootstrapping for modules that do not pass or that are built out of sequence:

          # build and deploy top-level artifact from root directory of git checkout
          mvn clean deploy -DskipTests
          # build the parent project. this will build and deploy all of the other artifacts as well.
          cd blazegraph-parent
          mvn clean deploy -DskipTests
          
          Show
          bryanthompson bryanthompson added a comment - See https://github.com/SYSTAP/bigdata/pull/69 for PR for changes per this ticket. We've agreed to do the following to get the snapshots published so the build should succeed without painful bootstrapping for modules that do not pass or that are built out of sequence: # build and deploy top-level artifact from root directory of git checkout mvn clean deploy -DskipTests # build the parent project. this will build and deploy all of the other artifacts as well. cd blazegraph-parent mvn clean deploy -DskipTests
          Hide
          bryanthompson bryanthompson added a comment - - edited

          I have followed that incantation and successfully deployed all snapshot artifacts while CI was busy with a non-maven build (GIT_DEVELOPMENT). I am now merging this change set down to the ticket_168 branch. CI will hopefully be well behaved.

          Note: The PR was NOT merged. We did this by hand instead. The PR was an attempt to merge to master. Which was NOT GOOD.

          Show
          bryanthompson bryanthompson added a comment - - edited I have followed that incantation and successfully deployed all snapshot artifacts while CI was busy with a non-maven build (GIT_DEVELOPMENT). I am now merging this change set down to the ticket_168 branch. CI will hopefully be well behaved. Note: The PR was NOT merged. We did this by hand instead. The PR was an attempt to merge to master. Which was NOT GOOD.
          Hide
          bryanthompson bryanthompson added a comment - - edited

          Many projects are building Ok. bigdata-jini has one weird error. I am trying to track down why the metavariable substitution is failing in this case. I suspect the "-" in the variable name.

          [WARNING] The POM for com.blazegraph:junit-ext:jar:${junit-ext.version} is missing, no dependency information available
          
          Show
          bryanthompson bryanthompson added a comment - - edited Many projects are building Ok. bigdata-jini has one weird error. I am trying to track down why the metavariable substitution is failing in this case. I suspect the "-" in the variable name. [WARNING] The POM for com.blazegraph:junit-ext:jar:${junit-ext.version} is missing, no dependency information available

            People

            • Assignee:
              beebs Brad Bebee
              Reporter:
              bryanthompson bryanthompson
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: