Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



Build the maven mojo

  1. You will need to BUILD this project first.

    $ export JAVA_HOME=/opt/sun-java2-8.0/; mvn clean install -DskipTests

Configure your JDK’s keystore

  1. NOTE: if your Jenkins/Hudson server runs on https, must first import its certificate or you may get this error:

    javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    1. AS USER (eg., using Firefox):

      Browse to https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/ & accept the cert. Log in using kerberos login.

      Menu/Edit > Preferences > Advanced > Certificates/Encryption > View Certificates > Servers
    2. Find the jenkins cert, then export to a file.

    3. AS ROOT:

      Import the cert to your existing JDK keystore(s), by running cert.import.sh.

      ./cert.import.sh /path/to/exported.cert
The default Java keystore password is changeit.
  1. Make sure that JAVA_HOME is set to the path where you imported the cert, eg.:

    export JAVA_HOME=/opt/sun-java2-8.0/; mvn clean install -f pom-sync.xml -Doperation=pull

Configure mojo usage

  1. Next, you need a pom file to drive the tool’s configuration, if you don’t want to have to pass in username/password/URL param every time on the commandline.

    Copy and edit pom-sync.xml to somewhere on your machine, perhaps the root folder where you have a cache of your config.xml files checked out.

Run the mojo

  1. Once your pom is configured with your credentials, you can use this tool. Invoke it by hand like this:

    $ export JAVA_HOME=/opt/sun-java2-8.0/; mvn clean install -f pom-sync.xml -Doperation=pull -DviewFilter=view/webtools_R3_10/ ...
  2. Or easier, use one of these scripts to push or pull files.

Commit changes

  1. After confirming your changes are pushed to the remote server, and didn’t break anything, you can commit the same changes to your local config.xml cache for storage/versioning.