Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-8499

Rice version is wrong in installation guide documentation for maven archetype (section 5, maven cli)

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.3, 2.2.0-rc1, 2.2
    • Component/s: Documentation
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I read the rice 2.1.2 release message and followed the link to the Installation Guide .

      In Section 5, "New Project Setup", "Maven CLI" there are two tables under point #1. The -DarchetypeVersion=2.2.0-M4-SNAPSHOT is wrong.

      I think it should be per rice version. i.e. on the 2.1.2 version of the rice docs it should be -DarchetypeVersion=2.1.2 not 2.2.0-M4-SNAPSHOT

      At this point in time the latest rice version is 2.2.0-RC1-SNAPSHOT so when I ran the documentation as described I recieved an error about the org.kuali.rice:rice-archetype-quickstart:2.2.0-M4-SNAPSHOT not existing.

      I looked at the latest documentation, the rice 2.1.2 documentation and the rice 2.2.0-M4 documentation and all the installation guides had the same content related to the version of the archetype.

        Attachments

          Activity

          Hide
          michael.ocleirigh Michael O'Cleirigh added a comment -

          I think the content in this section was created for KD2012 as documented in KULRICE-7774.

          Show
          michael.ocleirigh Michael O'Cleirigh added a comment - I think the content in this section was created for KD2012 as documented in KULRICE-7774 .
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          instead of hardcoding, we need to be using the maven variable. assigning to myself to update.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - instead of hardcoding, we need to be using the maven variable. assigning to myself to update.
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          updated to use the project.version variable so we don't run into this later.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - updated to use the project.version variable so we don't run into this later.

            People

            • Assignee:
              Unassigned
              Reporter:
              michael.ocleirigh Michael O'Cleirigh
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: