Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.3.2
    • Component/s: Packaging
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-4930Align SNAPSHOT release version numbers between various Rice Build artifacts
      KULRICE-5235Package 1.0.3.2 release
      KULRICE-1232Create a snapshot of the Rice 0.9.1 space
      KULRICE-1573Create 0.9.2 documentation snapshot for release
      KULRICE-50721.0.3.2 fixes for Tomcat 7 support
      KULRICE-5221Create SQL upgrade scripts for the 1.0.3.2 release
      KULRICE-4579Create a Rice 1.0.3 Milestone release for use by KS 1.1 Development
      KULRICE-7713Release new kuali commons-beanutils
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      KC is requesting that we push out another snapshot for them. Currently we have some unit test failures, but after those are fixed, we should push out the snapshot as soon as we can.

        Activity

        Hide
        Jeff Caddel (Inactive) added a comment - - edited

        A SNAPSHOT build of 1.0.3.2 is generated and published to Kuali's internal maven repo every night now.

        Each nightly build is tagged - https://test.kuali.org/svn/rice/tags/builds/1.0

        The corresponding artifacts can be downloaded directly via S3 - for example http://s3browse.springsource.com/browse/maven.kuali.org/snapshot/org/kuali/rice/rice-api/1.0.3.2-SNAPSHOT

        or

        via a Maven client that has been configured to point at the public Kuali Nexus instance - http://nexus.kuali.org/content/groups/public

        Show
        Jeff Caddel (Inactive) added a comment - - edited A SNAPSHOT build of 1.0.3.2 is generated and published to Kuali's internal maven repo every night now. Each nightly build is tagged - https://test.kuali.org/svn/rice/tags/builds/1.0 The corresponding artifacts can be downloaded directly via S3 - for example http://s3browse.springsource.com/browse/maven.kuali.org/snapshot/org/kuali/rice/rice-api/1.0.3.2-SNAPSHOT or via a Maven client that has been configured to point at the public Kuali Nexus instance - http://nexus.kuali.org/content/groups/public
        Hide
        Kristina Taylor (Inactive) added a comment -

        Thanks, I'm seeing the artifacts on Nexus now (strangely only after I clear my cache). Would it be possible to get javadocs and sources with those as well?

        Show
        Kristina Taylor (Inactive) added a comment - Thanks, I'm seeing the artifacts on Nexus now (strangely only after I clear my cache). Would it be possible to get javadocs and sources with those as well?
        Hide
        Jeff Caddel (Inactive) added a comment -

        The nightly process is now generating sources + javadocs

        Show
        Jeff Caddel (Inactive) added a comment - The nightly process is now generating sources + javadocs
        Hide
        Kristina Taylor (Inactive) added a comment -

        I'm seeing the artifacts on nexus, but the numbers are not matching up between the various modules. The latest rice-impl is 1.0.3.2-20110509.070454-10 but the latest rice-web is 1.0.3.2-20110509.070550-10, the difference being the 070454 versus the 070550. It would make it easier on us for our upgrade process to make these numbers the same; is that something that can be done?

        Show
        Kristina Taylor (Inactive) added a comment - I'm seeing the artifacts on nexus, but the numbers are not matching up between the various modules. The latest rice-impl is 1.0.3.2-20110509.070454-10 but the latest rice-web is 1.0.3.2-20110509.070550-10, the difference being the 070454 versus the 070550. It would make it easier on us for our upgrade process to make these numbers the same; is that something that can be done?
        Hide
        Jeff Caddel (Inactive) added a comment -

        The numbers in that section of the version number are different because it is a timestamp representing the moment in time the artifact was created. I would be wary of creating process that is tied to the timestamp portion of a snapshot build (or any given snapshot build in general). What are you trying to accomplish? Not sure if this will be useful for you, but there is a versioned milestone build going out today.

        Show
        Jeff Caddel (Inactive) added a comment - The numbers in that section of the version number are different because it is a timestamp representing the moment in time the artifact was created. I would be wary of creating process that is tied to the timestamp portion of a snapshot build (or any given snapshot build in general). What are you trying to accomplish? Not sure if this will be useful for you, but there is a versioned milestone build going out today.
        Hide
        Jeremy Hanson added a comment -

        I think KC is wanting to be able to specify a specific version dependency of rice to test with.

        That milestone build going out today is for Rice 2.0, so that wouldn't help here. Maybe KC needs a milestone release of 1.0.3.2 instead of nightly snapshots.

        Show
        Jeremy Hanson added a comment - I think KC is wanting to be able to specify a specific version dependency of rice to test with. That milestone build going out today is for Rice 2.0, so that wouldn't help here. Maybe KC needs a milestone release of 1.0.3.2 instead of nightly snapshots.
        Hide
        Jeff Caddel (Inactive) added a comment -

        Oh right, (thanks for clarifying that Jeremy). So yes, if they want to depend on a specific version of 1.0.3.2 instead of SNAPSHOT builds we'd need to establish some process around creating versioned builds of the 1.0 branch.

        Show
        Jeff Caddel (Inactive) added a comment - Oh right, (thanks for clarifying that Jeremy). So yes, if they want to depend on a specific version of 1.0.3.2 instead of SNAPSHOT builds we'd need to establish some process around creating versioned builds of the 1.0 branch.
        Hide
        Jessica Coltrin (Inactive) added a comment -

        I think that Sam and Farooq may have already tackled this. While on vacation, Farooq saw an email from Kristina on a KC list and sent me this:

        First run UT-1.0.3.2-mysql to make sure no errors and then run rice-1.0.3.2-deploy-snapshots to deploy snapshot.

        This should do what they had before. Hopefully it's useful.

        Show
        Jessica Coltrin (Inactive) added a comment - I think that Sam and Farooq may have already tackled this. While on vacation, Farooq saw an email from Kristina on a KC list and sent me this: First run UT-1.0.3.2-mysql to make sure no errors and then run rice-1.0.3.2-deploy-snapshots to deploy snapshot. This should do what they had before. Hopefully it's useful.
        Hide
        Jessica Coltrin (Inactive) added a comment -

        closing since 1.0.3.2 is released.

        Show
        Jessica Coltrin (Inactive) added a comment - closing since 1.0.3.2 is released.

          People

          • Assignee:
            Jeff Caddel (Inactive)
            Reporter:
            Jeremy Hanson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel