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

Add all provided modules as a special profile to the main build pom

    XMLWordPrintable

    Details

    • Type: Task
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Incorporated
    • Affects Version/s: 10.0, 11.0
    • Fix Version/s: None
    • Component/s: Release Management
    • Labels:
      None

      Description

      For the 10 release, we were thinking about just deploying all jars that are marked as provided rather than all jars. (That are expected to be found by other tools)

      This can be built with mvn clean install -P sakai-provided

      There is a process for creating this section.
      https://github.com/jonespm/sakai-listdir-plugin

      There might be a few exceptions of jars that are needed at compile, and these might need to also be released. Exceptions already included are jsf and velocity. portal-util has come up as one that might need to be an exception.

      For the most part, people will still need to build all of Sakai to build everything, but releasing apis and these artifacts that are more static should make it easier for some contrib tools, libraries that depend on sakai's internal apis and certain special build patterns.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jonespm Matthew Jones
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code