PragmaticKM Parent Changelog


Release Notes

  • To significantly reduce the size of Javadocs, using new AO Javadoc Resources project instead of data: URLs.


Release Notes


Release Notes

  • Changed Include-Resource to {maven-resources}, target/resources-filtered in order to not leak full build paths into META-INF/MANIFEST.MF


Release Notes

  • Updated version of AO OSS Parent.
  • New profile "POST-SNAPSHOT" that enables the use of post-release builds as dependencies.

    This profile is not active by default. Activate in ~/.m2/settings.xml to use post-release builds as dependencies:


    This profile must not be active while performing a release. Deactivate with:

    mvn -Prelease,'!POST-SNAPSHOT' …

    Post-release builds happen after a release and before a new -SNAPSHOT is started. They are used to ensure that previous releases still compile against newer dependencies.

    Furthermore, post-release builds may contain the following changes without being promoted to the next -SNAPSHOT version:

    1. Updated parent POM
    2. Updated POM
    3. Updated Java version (without any source code changes)
    4. Updated dependency versions
    5. Updated javadocs
    6. Updated documentation
    7. Updated unit tests
    8. Deprecated methods and classes
    9. Renamed private fields and local variables
    10. Other changes to white-space or comments

    Post-release builds also allow NetBeans to correctly connect projects together for those who are actively developing multiple modules.

    Those who are only using the dependency can use the regular release to avoid the overhead of the daily check for updates.


Release Notes


Release Notes

  • License changed to LGPL v3.
  • Moving PragmaticKM to GitHub and Maven Central Repository.


Release Notes

  • Added --allow-script-in-comments for Javadoc in JDK 1.8.0_121+.
  • Updated dependencies.


Release Notes

  • New parent POM, separate from aggregator POMs, to allow the addition of modules without having to also release untouched modules within the same overall project.

    Previously, adding a module to the aggregator would increment its version, which would then propagate all the way down to update the parents of all modules. Since our projects are extremely modular, this forced releases where only the parent version was modified.

    We recommend a separation of parent and aggregator pom.xml for any multi-module Maven project where each module is released independently.