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

Document policy for snapshot generation, publication, and inclusion

    Details

    • Type: Sub-task
    • Status: Done
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: BLAZEGRAPH_2_0_0
    • Component/s: None
    • Labels:
      None

      Description

      BLZG-37 is a dependency problem. Once we document how the generated artifacts are to be published and resolved I can resolve that ticket.


      *Current Policy: *

      The development branches all specify the version as follows. This assumes that we are in the development process leading up to a 1.5.2 release, which is currently true. With this setting made consistently in the pom for each bigdata/blazegraph module the modules will build from mutually consistent snapshots.

      <version>1.5.2-SNAPSHOT</version>
      

      General Policy: TBD

      We need a more general policy that will allow us to run maven CI builds on branches without causing interactions with the maven CI builds on master.

      When changing versions

      Changing versions can get the CI builds out of whack, especially if some of the CI jobs have tests that fail (since in this case they will not deploy their artifact and downstream projects can not succeed). The following incantation can be used to force deployment of the snapshot artifacts so the CI build can succeed:

      # 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
      

      Understanding versions

      mvn dependency:tree
      

        Issue Links

          Activity

          Hide
          beebs Brad Bebee added a comment -

          checkout ticket_168
          mvn clean install deploy -DskipTests
          cd blazegraph-parent
          mvn clean install deploy -DskipTests

          Show
          beebs Brad Bebee added a comment - checkout ticket_168 mvn clean install deploy -DskipTests cd blazegraph-parent mvn clean install deploy -DskipTests
          Hide
          beebs Brad Bebee added a comment -

          I updated the versions on the ticket_168 branch to use the SNAPSHOT-1.5.2 version. This should reduce (eliminate) collisions with other artifacts deployed from the non-maven branches.

          Show
          beebs Brad Bebee added a comment - I updated the versions on the ticket_168 branch to use the SNAPSHOT-1.5.2 version. This should reduce (eliminate) collisions with other artifacts deployed from the non-maven branches.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: