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

Prep LessonBuilder poms for off-cycle releases



    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.9.0
    • Fix Version/s: 2.9.0
    • Component/s: Lessons
    • Labels:
    • Previous Issue Keys:


      Prepping LessonBuilder poms to utilize the release plugin. Also tidy up the poms as necessary.

      1. Change the <groupId> to org.sakaiproject.lessonbuilder. LB's coordinates will adhere to the pattern adopted for other indies, which is reflective of broader Maven naming practices including that practiced by Apache.

      2. Change trunk versionId to 1.3-SNAPSHOT. This is necessary because it reflects accurately the unstable nature of trunk and is required in order for Maven to deploy snapshot artifacts to the snapshot repo.

      3. Set up LB so that we can deploy binaries to the snapshot repo. Basically boilerplate additions to the base pom. Add <distributionManagement>, <repositories>, <pluginRepositories> and <reporting> declarations to base pom. Update the current Jenkins job to deploy snapshot updates.
      example: https://source.sakaiproject.org/svn/basiclti/trunk/pom.xml

      4. Add an assembly which provides a Tomcat-overlay zip of LB. As I noted in LA we will not substitute an assembly for a full source check out of LB but the assemblies have proven quite useful to msub deployers such as Steve Swinsburg. Plus, if we ever get the app store concept going a zip of LB binaries will prove quite useful. Again, this code, a pom file and deploy.xml is largely boilerplate. It takes about 5 minutes to write.
      example: https://source.sakaiproject.org/svn/basiclti/trunk/basiclti-assembly/

      5. Set LB up to use the release plugin. Involves swapping out the master pom for the edu-tool purepom like other indies. We have 2.6, 2.7, 2.8, 2.9 versions of purepoms. I expect that LB will benefit from use of the release plugin (which the purepoms provide) which provides the ability to generate off-cycle releases in a simple, nay trivial manner.

      6. Tidy up the poms. For example, substitute standard Maven variables such as ${project.groupId} and ${project.version} where appropriate for LB's own "internal" dependencies.

      7. Delete tool/src/maven2 folder. It is now redundant as updated sakairsf 0.8-SNAPSHOT artifacts exist.

        Gliffy Diagrams



              Issue Links



                  arwhyte Anthony Whyte
                  arwhyte Anthony Whyte
                  0 Vote for this issue
                  0 Start watching this issue



                      Git Integration