Skip to content

Releases: jenkinsci/custom-war-packager

v2.0-alpha-6

24 May 14:23
Compare
Choose a tag to compare
v2.0-alpha-6 Pre-release
Pre-release

πŸš€ New features and improvements

πŸ“¦ Dependency updates

πŸ‘» Maintenance

v2.0-alpha-5

05 Oct 09:31
Compare
Choose a tag to compare

πŸ› Bug Fixes

πŸ“¦ Dependency updates

πŸ“ Documentation updates

πŸ‘» Maintenance

v2.0-alpha-3

24 Jul 10:01
Compare
Choose a tag to compare
v2.0-alpha-3 Pre-release
Pre-release

πŸš€ New features and improvements

  • Add a --updateCenterUrl CLI argument (#135) @gurv
  • Support configuring Maven repositories via buildSettings/jenkinsRepository (#135) @gurv
  • Improve error message when Git tag or branch cannot be found (#161) @oleg-nenashev

πŸ› Bug Fixes

  • Fix support of the --updateCenterUrl option in the Custom WAR Packager library (#135) @gurv

πŸ“¦ Dependency updates

πŸ“ Documentation updates

πŸ‘» Maintenance

v2.0-alpha-2

15 Aug 08:50
Compare
Choose a tag to compare
v2.0-alpha-2 Pre-release
Pre-release

πŸš€ New features and improvements

  • Move bomIncludeWAR to buildSettings, split out pomIncludeWAR to a separate setting (breaking change) (#114) @oleg-nenashev

πŸ“ Documentation updates

πŸ‘» Maintenance

1.7

11 Aug 21:12
Compare
Choose a tag to compare
1.7

This is a first Custom War Packager 1.x stable release. New development will happen as a part of the the 2.x branch which is now in alpha.

πŸ› Bug Fixes

  • JENKINS-57547 - Fix processing of Core dependencies to prevent failures in reading plugins from pom.xml (regression in 1.6) (#99) @oleg-nenashev
  • #66 - Fix the Error assembling WAR: webxml attribute is required error on some configurations (#67) @alxsap
  • [JENKINS-55832] - Fix the Artifact Manager S3 demo so that it can be actually used (backported from #104) @oleg-nenashev

πŸ“ Documentation updates

🚦 Internal changes

2.0-alpha-1

11 Aug 21:49
Compare
Choose a tag to compare
2.0-alpha-1 Pre-release
Pre-release

πŸ’₯ Breaking changes

  • Use the Update Center Plugin plugin info Provider by default. The previous Maven provider can be reenabled on-demand. See Plugin Information Providers for more info

πŸš€ New features and improvements

  • JENKINS-55832 - Introduce new Update Center Plugin plugin info provider for pom.xml plugin inputs. This provider greatly improves the build time for common configurations (#104) @oleg-nenashev
    • Documentation: Plugin Information Providers
    • NOTE: The provider will be unable to install plugins which have not been deployed to the target update center yet. It is also essential to specify a proper update center if custom plugins are used, Jenkins official update center is used by default.

πŸ“¦ Dependency updates

1.6

25 May 11:11
Compare
Choose a tag to compare