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

POM changes required for releases via Maven 3

    Details

    • Type: Task
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Incorporated
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Maven
    • Labels:
      None

      Description

      From https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html

      Unlike Maven 2, Maven 3 supports out of the box only http:, https: and file: as transport protocols. To use other transport protocols like scp:, the appropriate wagons have to be explicitly declared in the POM as a build extension. If the wagon in question is only used for deployment to a repository, it can alternatively be declared as a dependency of the Maven Deploy Plugin.

      Therefore, for us to release using Maven3 we need to use the extension.

      This has also become an issue for us in Maven 2 when using OS X 10.7. There was a repeated prompt for the password event though we are using ssh keys, the maven settings were correct, and ssh to the box works without password.

      The required mods are simply:

      1. Change all deployment urls to be the scpexe protocol (i.e. every url in distribution management, including the site url)
      2. Add this to the <build> block:

      <extensions>
      <!-- Enabling the use of external ssh -->
      <extension>
      <groupId>org.apache.maven.wagon</groupId>
      <artifactId>wagon-ssh-external</artifactId>
      <version>2.0</version>
      </extension>
      </extensions>

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

              1.
              Site POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              2.
              Assignment POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              3.
              Announcement POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              4.
              Calendar POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              5.
              emailtemplateservice POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              6.
              JobScheduler POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              7.
              JSF POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              8.
              Message POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              9.
              Metaobj POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              10.
              Presence POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              11.
              Profile POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              12.
              sakai-mock POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              13.
              taggable POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              14.
              velocity POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              15.
              webservices POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              16.
              courier POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              17.
              content-review POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              18.
              mail-archive POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              19.
              portal POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              20.
              site-manage POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              21.
              entitybroker POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte
              22.
              warehouse POM changes required for releases via Maven 3 Sub-task CLOSED Anthony Whyte

                Activity

                  People

                  Assignee:
                  Unassigned Unassigned
                  Reporter:
                  steve.swinsburg Steve Swinsburg
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration