Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-2287

Fix release process for optional modules (e.g. LNI and Mirage2)

    Details

    • Type: Task
    • Status: Volunteer Needed (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      1
    • Documentation Status:
      Needed

      Description

      When releasing DSpace 5.0RC1, we stumbled on the fact that optional modules (i.e. those not built by default) are also NOT included in the release process by default.

      So, simply running "mvn release:prepare" builds ONLY the default modules, and leaves out both LNI and Mirage2 from the release process.

      Instead, as a workaround we've been forced to run:
      mvn release:prepare -Dmirage2.on=true -Pdspace-lni
      mvn release:perform -Dmirage2.on=true -Pdspace-lni

      We need to investigate whether there's a way to enable these optional modules automatically in the release process.

      One possible option is to rework/refactor our POMs as described here: http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/
      Currently our practice has been to do exactly what is recommended against. If we can refactor as suggested, this might help. But, it's unproven as of yet.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                tdonohue Tim Donohue
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: