SemanticCMS Parent Changelog

1. Java 20 is now end-of-life
2. Java 21 is now current stable
3. Java 22 is new beta

New property ${subproject.subpath} that is the path to the sub-project. This should be empty for the top-level project or the path (ending in slash) to append to ${project.url}.

One important use is the offsetting of the generated Javadoc apidocs/ URL. This is because others may publish our sub-project API docs that we do not publish directly (such as books). When published, we do not want conflicting canonical URLs.

Sub-projects that both share the same ${project.url} and generate Javadocs must override this value.

Enabled jacoco-maven-plugin in <reporting> (generated site reports).

Please note that mvn site is currently broken due to MSITE-973. We expect this problem to be resolved when maven-site-plugin-4.0.0-M10 is released.

1. Patches timestamps from the last build for entries that are not modified. These optimized reproducible artifacts accomplish the following:
   1. Fine-grained timestamp tracking of AAR/JAR/WAR/ZIP artifact entries
   2. Reduced number of distinct build artifacts
   3. Correct maintenance and propagation of last-modified time for caching layers, clients, and related tools such as sitemap generators
2. SEO filtering of Javadocs, including canonical meta tags, robots noindex, rel="nofollow" links, and XML sitemaps.

release:prepare has no way to avoid it replacing ${git.commit.time} with a fixed ISO8601 timestamp. Having a fixed timestamp has some arguable benefits regarding build reproducibility, so we're not going to fight this.

Releases now use fixed ISO8601 timestamps while snapshots continue to use ${git.commit.time}. This means that all child projects must define their own ${project.build.outputTimestamp} property in order to not inherit the timestamp of the parent during releases.

Since releases no longer depend on ${git.commit.time}, the git-commit-id-maven-plugin goals are disabled under the release profile.

We also added an enforcer rule to ensure ${project.build.outputTimestamp} is correctly set back to ${git.commit.time} after a release.

1. Implementation-Version now uses correct OSGi version format. Previously was using ${project.version}, but now uses ${parsedVersion.osgiVersion} from build-helper:parse-version.
2. Added _nouses to avoid NP-hard time complexity in "uses" resolvers.

Using packaging=jar instead of packaging=bundle for all jar projects. OSGi manifest entries are still added, however, as documented at Adding OSGi metadata to existing projects without changing the packaging type. This has the side effect that projects that were previously packaging=jar will now have OSGi manifest entries added. None of our projects were previously of the jar packaging.

This change is required since maven-bundle-plugin has been adding entries with a constant and hard-coded timestamp of 1980-02-01.

These constant timestamps are incompatible with the automatic lastModified parameters added by AO Servlet Last Modified when the resource is contained in a JAR file within WEB-INF/lib. This has resulted in browsers using out-of-date cached content.

1. Java 19 is now end-of-life
2. Java 20 is now current stable
3. Java 21 is new beta

1. Removed Implementation-Build-Date from all manifest.
2. Set notimestamp in maven-javadoc-plugin.
3. build.currentYear property is now extracted from project.build.outputTimestamp. As a result, buildnumber-maven-plugin is no longer part of the build.
4. Upgraded maven-javadoc-plugin from 3.0.1 to 3.4.1. Due to MJAVADOC-682 not yet resolved, builds will revert to version 3.0.1 under a new "reactor" profile.
5. Changed Jenkins builds from Java 11 to Java 17.
6. Jenkins builds now use .m2/repository-jdk-${jdk} for all Java versions. Previously, builds for ${deployJdk} used .m2/repository. This change makes it unnecessary to rename local repositories when changing ${deployJdk}.

1. Added Jakarta EE 10

1. Java 18 is now end-of-life
2. Java 19 is now current stable
3. Java 20 is new beta

Enabled Checkstyle on all builds using Apache Maven Checkstyle Plugin.

The default style is based on Google's Java Style Checkstyle, but with the maximum line length increased to 200 characters.

By default, builds fail on Checkstyle error. Each project that cannot immediately be adapted to pass the analysis should configure the plugin with <failOnViolation>false</failOnViolation>.

Enabled SpotBugs on all builds using SpotBugs Maven Plugin.

By default, builds fail on SpotBugs error. Each project that cannot immediately be adapted to pass the analysis should configure the plugin with <failOnError>false</failOnError>.

1. Java 16 is now end-of-life
2. Java 17 is now current stable
3. Java 18 is new beta

1. Enforces "development" profile is also active
2. Disables PGP artifact verification
3. Disables GPG artifact signing

1. Default version changed from Java™ EE 6 to Java™ EE 7
2. Updated apidocs URL for Jakarta EE 8
3. Added Jakarta EE 9
4. Added Jakarta EE 9.1

Several profiles may now be conveniently activated by the presence of files in an optional profile.d directory. This technique is primarily a workaround for profiles not being able to be activated by properties of sub-projects, and has the added benefit that the set of profiles across all projects is easily manipulated through Bash scripts.

This includes maven.javadoc.skip, maven.install.skip, maven.deploy.skip, and skipNexusStagingDeployMojo, which all have the expected skipping behavior matching the property of the same name.

1. Java 15 is now end-of-life
2. Java 16 is now current stable
3. Java 17 is new beta

Switched back to generating Javadocs links with target="_top" on all versions of Java. Eventhough the API Docs are generated without frames as of Java 9, they may still be used within frames in other contexts, such as when viewed at https://javadoc.io/.

Furthermore, browsers are increasingly blocking or issuing warnings when a link tries to go to a different site within a frame. This change ensures links always escape frames.

1. Java 14 is now end-of-life
2. Java 15 is now current stable
3. Java 16 is new beta

Set <detectOfflineLinks>false</detectOfflineLinks> on maven-javadoc-plugin.

Projects are built and released on an individual basis, and thus we manually link between projects to not rely on reactor / aggregator builds to achieve proper linking.

Furthermore, we maximize the use of offline links from javadoc artifacts. This has several benefits:

1. Repeatable builds: linking is done against the specified version versus whatever is published online
2. More reliable build: does not depend on external apidocs server to be online
3. Higher build performance: uses locally cached artifacts instead of http/https requests on each build
4. Offline builds: when all artifacts are already locally available
5. Private builds: linking to apidocs from private projects not publicly available
6. Chicken-and-Egg resolved: can link between projects before publishing any of them
7. New version linking: links are properly created before releasing new versions

Default <links /> converted to <offlineLinks /> on maven-javadoc-plugin, taking advantage of the new AO Javadoc Offline project. Furthermore, the offline links also include JavaMail and Java EE.

Offline links are enabled by the new offlineLinks profile, which is activated by the presence of src/main/java. If desired, this profile may be deactivated during a build with mvn -P'!offlineLinks' ….

One notable consequence is that Javadocs are now fully formatted without requiring the release profile.

Enabled the wagon-ssh-external extension on all projects, which supports access to artifact repositories via scpexe://… URLs.

Projects that have access to their parent either directly or over HTTP/HTTPS may remove wagon-ssh-external from their .mvn/extensions.xml. However, if the parent is accessed through scpexe://…, the declaration in extensions.xml is still required.

1. Configured manifest entries consistent with other plugins.

1. Added filtered web resources src/main/webapp-filtered, which is expected to include a META-INF/context.xml. This means that projects must have a src/main/webapp-filtered directory, even if just an empty directory.
2. Excluded src/main/webapp/META-INF/context.xml so that the filtered version may be used. This file still must be present, however, as NetBeans uses this file to determine how to deploy to local development Tomcat.
3. META-INF/context.xml is not included in the WAR file. The expectation is production values will be provided by the container.

Newer versions of Javadocs no longer use frames. We now build API docs with target="_self" for JDK >= 9.

We still support building with older JDK versions, in which target="_top" is used so that links can escape the frames.

1. Consolidated build properties compiler.bootclasspath and javac.bootclasspath into a single property java.bootclasspath.
2. javaVersion to javase.version
3. javac.link.javaApi to javadoc.link.javase
4. javac.link.javaApi.jdk* to javadoc.link.javase.*
5. javac.link.javaeeApi.* to javadoc.link.javaee.*
6. javac.link.javamailApi to javadoc.link.javamail
7. java.bootclasspath to javase.bootclasspath
8. javase.bootclasspath* to javase.bootclasspath.*
9. documented.javaVersion to documented.javase.version
10. documented.javac.link.javaApi to documented.javadoc.link.javase

1. javaee.version,default 6
2. javadoc.link.javaee, default ${javadoc.link.javaee.6}
3. documented.javaee.version, default 6
4. documented.javadoc.link.javaee, default ${javadoc.link.javaee.6}

• Changed lockMode to a fixed value "multiple"
• Removed defaultKeyring
• Removed useAgent
• Removed publicKeyring
• Removed secretKeyring

1. Java 13 is now end-of-life
2. Java 14 is now current stable
3. Java 15 is new beta

Set delimiters for maven-war-plugin to match the configuration of maven-resources-plugin, using @{*}.

Also enabled filteringDeploymentDescriptors by default.

1. Java 12 is now end-of-life
2. Java 13 is now current stable
3. Java 14 is new beta

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

    <profile>
      <id>POST-SNAPSHOT</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <properties>
        <POST-SNAPSHOT>-POST-SNAPSHOT</POST-SNAPSHOT>
      </properties>
    </profile>

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.

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.