Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-37377

Revise LB poms so that we can perform separate API and tool releases

    XMLWordPrintable

    Details

    • Type: Task
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.9.0
    • Fix Version/s: 2.9.0
    • Component/s: Lessons
    • Labels:
      None

      Description

      As discussed in the LA project planning meeting one change we intend to make for 2.9+ is to perform API releases independently and ahead of tool releases. In the case of LB, sometime after code freeze we would release sakai-lessonbuilder-api-1.0 (or 1.2 whatever you want). In order to do this we will need to replace the api's current <parent> (the LB base pom) with a purepom-like "sakai api" pom that will be released first so that an LB api release can actually be performed (currently, you can't do a release of an api that has a snapshot dependency on its own project base pom). Ideally, once we hit code freeze, we release the kernel apis, then all the tool apis. We should then be able to better reflect version-wise the actual steady state of most project apis. LB tool 1x tool releases should then be able to bind to lessonbuilder-api-1.0 for the life of the 1x series.

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                Assignee:
                arwhyte Anthony Whyte
                Reporter:
                arwhyte Anthony Whyte
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration