amuniz / maven-hpi-plugin Goto Github PK

Maven plugin to build Jenkins plugins. See the developer guide for details.

Mojo documentation

Changelog

2.0 (2017 May 25)

• Updated integrated Jetty server to 9.x. This means that JDK 8 is now required at build time. (Plugins may continue to target older Java baselines using the java.level property in the 2.x parent POM.)
• JENKINS-24064 Added executable-war artifact type, permitting Jenkins to stop deploying the wasteful jenkins-war-*-war-for-test.jar artifact, which was identical to jenkins-war-*.war.

1.122 (2017 Apr 12)

• Fixed HTML escaping for Javadoc created for taglibs so it can be processed by JDK 8.
• Logging the current artifact for InjectedTest.
• More fixes to mojos that assumed that plugin artifacts used a short name identical to the artifactId.
• Minor archetype updates.

1.121 (2016 Dec 16)

• Fixing a problem with plugin dependency resolution affecting users of jitpack.io.

1.120 (2016 Sep 26)

• Allowing hpi:run to pick up compiled classes & saved resources from core or plugin snapshot dependencies in addition to the plugin under test itself.
• Ensuring Plugin-Dependencies appears in a consistent order from build to build.

1.119 and earlier

Not recorded.

For maintainers

mvn -Prun-its clean install
# Find some plugin using the 2.x parent POM and run:
mvn -f ../some-plugin -Dhpi-plugin.version=2.XXX-SNAPSHOT -DskipTests -DjenkinsHome=/tmp/sanity-check-maven-hpi-plugin clean package hpi:run

You can also rerun one test:

mvn -Prun-its mrm:start invoker:run mrm:stop -Dinvoker.test=parent-2x

To rerun just the verification script:

groovy -e "basedir='$(pwd)/target/its/parent-2x'; evaluate new File('src/it/parent-2x/verify.groovy')"

Also make sure project.parent.version in src/it/parent-2x/pom.xml is the latest.

Updating Jetty

hpi:run mojo is a variant of jetty:run mojo, and because of the way plugin descriptor is generated, this module copies some code from Jetty Maven plugin, specifically AbstractJettyMojo.java and ConsoleScanner.java.

To keep upstream tracking easier, prestine copies of these files are copied into incoming-x.y branch, then package renamed. This version specific incoming branch is then "theirs" merged into the incoming branch, which acts as the upstream tracking branch.

This branch is then merged into master via git merge -X ignore-space-at-eol incoming. See diff between incoming and master on these files to see the exact local patches.