Uploaded image for project: 'Contrib: Yaft'
  1. Contrib: Yaft
  2. YAFT-42

CLONE - POM changes required for releases via Maven 3


    • Type: Task
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.x
    • Component/s: Yaft
    • Labels:


      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:

      <!-- Enabling the use of external ssh -->

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  steve.swinsburg Steve Swinsburg
                  steve.swinsburg Steve Swinsburg
                • Votes:
                  0 Vote for this issue
                  0 Start watching this issue


                  • Created:

                    Git Source Code