New ${notDevMode} property that is the negation of the existing ${devMode} property. It will be false only when the "development" profile is active and true otherwise.
New set of publish.tomcat7-maven-plugin.* profiles that centralize configuration of deployments via tomcat7-maven-plugin. Profiles are enabled in profile.d/ and configured via properties. Supports:
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.
Build steps selection is much more based on properties, where the phase is set to "none" to disable. Although not 100%, this is a major step in this direction.
Google Analytics tracking code is no longer added using the <bottom> section in maven-javadoc-plugin. Instead, the tracking code is added by the build of the website publishing the API docs using the newAO Ant Tasks project. Importantly, the tracking code is no longer included in Javadocs released to Maven Central.
GPG signing may be skipped with new profile activated by presence of profile.d/maven.gpg.skip. When active, the maven.deploy.skip, maven.install.skip, andskipNexusStagingDeployMojo profiles must also be active. This is primarily used for projects that only run directly in NetBeans.
To fully satisfy Central Repository Requirements, all projects must deploy javadoc classifier when have any *.java file, even if only a module-info.java. Projects that have no public API now generate a placeholder javadoc artifact, with the index.htmldescribing the reason why Javadocs are not present. The generated artifacts also contain an empty element-list.
nmw-oss-parent-1.20.1
Release Links
Release Notes
Avoiding second invocation ofbundle:manifestduring Jenkins "Deploy" stage. The second invocation was polluting the MANIFEST.MF with an extra entry Originally-Created-By: Apache Maven Bundle Plugin 5.1.9.
Reproducible build ${project.build.outputTimestamp} set back to ${git.commit.time}. The property was replaced with a fixed timestamp byMaven Release Plugin during the last release. This caused all child projects to incorrectly use the time that the parent was released, not that of the project's last commit as intended.
Only doing the second filtering pass of src/main/resources-filtered for packaging type "bundle", which none of our projects currently use. This is a workaround forbundle:bundlenot including filtered resources directly. This also results in a cleaner and more reproducibleMANIFEST.MF, with Include-Resource no longer including${project.build.directory}/resources-filtered.
release:preparehas 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}, thegit-commit-id-maven-plugingoals 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.
OSGi improvements:
Implementation-Version now uses correct OSGi version format. Previously was using ${project.version}, but now uses ${parsedVersion.osgiVersion} frombuild-helper:parse-version.
New ${devMode} property that will be true only when the "development" profile is active. "publish" profile may not be activated at the same time as "development" profile.
nmw-oss-parent-1.20.0
Release Links
Release Notes
Reproducible build ${project.build.outputTimestamp} is now based off ${git.commit.time}via git-commit-id-maven-plugin.
Using packaging=jar instead of packaging=bundle for all jar projects. OSGi manifest entries are still added, however, as documented atAdding 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-pluginhas 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 byAO 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.
nmw-oss-parent-1.19.0
Release Links
Release Notes
Updated plugin versions.
New automatic profile for per-project PGP keys mapvia pgp-keys-map.list file in project root.
New build property ${build.versionNoPostSnapshot} that contains the project version number without any trailing -POST-SNAPSHOT. For example, version 1.2.3-SNAPSHOT remains1.2.3-SNAPSHOT while both 1.2.3 and 1.2.3-POST-SNAPSHOT become1.2.3.
build.currentYear property is now extracted from project.build.outputTimestamp. As a result, buildnumber-maven-plugin is no longer part of the build.
Upgraded maven-javadoc-pluginfrom 3.0.1 to 3.4.1. Due to MJAVADOC-682not yet resolved, builds will revert to version 3.0.1 under a new "reactor" profile.
Changed Jenkins builds from Java 11 to Java 17.
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}.
Limited the workaround for JDK-8215291to only builds in JDK < 12 with no src/main/java/module-info.java. The previous mitigation was applied too broadly and broke the search URLs for projects with modules.
Reduced size of Javadoc top section and fixed scroll position in Java 11.
Enabled Checkstyle on all builds usingApache 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 usingSpotBugs 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>.
An alternate build directory (other than the default target) may now be selected by providing an alt.build.dirproperty. We use this in continuous integration to be able to concurrently build a project for multiple JDK versions, significantly reducing the build time.
Added new "coverage" profile that enables JaCoCo unit test code coverage. This is expected to primarily be used within continuous integration systems, and may be used as a basis forSonarCloud/SonarQube analysis.
Now verifying artifact PGP signatureson all builds. This means that GPG signing is now performed for all builds, including local-only builds with the "development" profile active.
Enabled dependency bytecode version checkson builds. This will ensure a project does not inadvertently depend on a library of a newer Java version than the project itself. The check is skipped when the development profile is active.
Updated plugin versions.
Bundle-SymbolicName is now defined to be the same as Java 9+ module names.
The "release" profile is now only to be used for production non-SNAPSHOT releases. SNAPSHOT builds should only use the "POST-SNAPSHOT" profile. Local development builds should now use the "development" profile, and may optionally use the "POST-SNAPSHOT" profile.
Reverted maven-dependency-plugin from version 3.2.0 to 3.1.2 untilIssue 753 is resolved.
Reverted maven-javadoc-plugin from version 3.3.0 to 3.0.1 since reactor builds are failing with "Exit code: 1 - error: module not found: …" on projects with Java 9+ modules. Please see Issue 682.
Several profiles may now be conveniently activated by the presence of files in an optionalprofile.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.
Nexus Repository Manager URL is now defined in a $nexusUrl property. The URL should end with a slash (/) and is used for both distributionManagement/snapshotRepository and nexus-staging-maven-plugin/nexusUrl. Defaults to https://oss.sonatype.org/since groupId com.newmediaworks is on the original Sonatype Nexus Repository Manager.
nmw-oss-parent-1.12.1
Release Links
Release Notes
Java updates:
Java 15 is now end-of-life
Java 16 is now current stable
Java 17 is new beta
nmw-oss-parent-1.12.0
Release Links
Release Notes
Updated plugin versions.
Removed offline Javadocs for com.servlets:cos, since we have eradicated it from all projects in favor ofthe standard file upload APIand JavaMail.
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.
New build properties ${build.isSnapshot} and ${build.notSnapshot}that are set to true or false, depending in whether the${project.version} is, or is not respectively, *-SNAPSHOT.
Now automatically configures rulesUrifor versions-maven-pluginwhen the versions-rules.xml file exists, via a new versions-rules profile.
Updated plugin versions.
nmw-oss-parent-1.8.0
Release Links
Release Notes
Corrected the default value for the Maven build property documented.javadoc.link.javaee.
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:
Repeatable builds: linking is done against the specified version versus whatever is published online
More reliable build: does not depend on external apidocs server to be online
Higher build performance: uses locally cached artifacts instead of http/https requests on each build
Offline builds: when all artifacts are already locally available
Private builds: linking to apidocs from private projects not publicly available
Chicken-and-Egg resolved: can link between projects before publishing any of them
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' ….
Moved configuration into <pluginManagement /> where appropriate. One notable consequence is that Javadocs are now fully formatted without requiring the release profile.
Restored Built-By manifest entry on bundle and war packaging.
Now supporting generated resources on all projects.
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 removewagon-ssh-external from their .mvn/extensions.xml. However, if the parent is accessed through scpexe://…, the declaration in extensions.xmlis still required.
Configured manifest entries consistent with other plugins.
Changed Built-By manifest entries from defaulting to blank to now defaulting to ${project.organization.name}.
Enabled <attachClasses>true</attachClasses>on maven-war-plugin whensrc/main/java exists. This allows the classes to by used as a dependency. This is particularly useful for our multi-project translation tools.
Set <trimStackTrace>false</trimStackTrace>on maven-surefire-plugin. The full stack traces of exceptions during testing should help in debugging.
Defined default build resources of both src/main/resources and src/main/resources-filtered (filtered). Previously, we had obtained this behavior through configuring plugins directly, but missed the more proper approach of defining in project/build/resources. This cleans-up the implementation, and allows other parts of the configuration to work correctly when projects define different or additional resources.
Defined default test resources of both src/test/resources and src/test/resources-filtered (filtered). This is for consistency with the definition of compilation resources.
Configured maven-war-plugin to support filteredMETA-INF/context.xml, which is used to provide development values to web applications:
Added filtered web resources src/main/webapp-filtered, which is expected to include a META-INF/context.xml. This means that projectsmust have a src/main/webapp-filtered directory, even if just an empty directory.
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.
META-INF/context.xml is not included in the WAR file. The expectation is production values will be provided by the container.
nmw-oss-parent-1.5.1
Release Links
Release Notes
nmw-oss-parent-1.5.0
Release Links
Release Notes
Changed default Java version from 1.7 to 1.8
Reduced use of property substitutions in pom.xml. This is to help 3rd-party parsers that fail to perform full Maven-compatible substitutions.
Now setting build properties maven.compiler.source and maven.compiler.target.
Now setting build property javadoc.link.javamail in parent POM instead of on a per-project basis.
Now setting builds properties documented.javase.version and documented.javadoc.link.javasein parent POM, with the default Java version (currently 1.8). This allows books to not specify the Java version of the documented project when it is the default.
Renamed some build properties to better represent their usage:
Consolidated build properties compiler.bootclasspath and javac.bootclasspathinto a single property java.bootclasspath.
javaVersion to javase.version
javac.link.javaApi to javadoc.link.javase
javac.link.javaApi.jdk* to javadoc.link.javase.*
javac.link.javaeeApi.* to javadoc.link.javaee.*
javac.link.javamailApi to javadoc.link.javamail
java.bootclasspath to javase.bootclasspath
javase.bootclasspath* to javase.bootclasspath.*
documented.javaVersion to documented.javase.version
documented.javac.link.javaApi to documented.javadoc.link.javase
Renamed profile bootclasspaths to javase.bootclasspath.
Changed Include-Resource to {maven-resources}, target/resources-filteredin order to not leak full build paths into META-INF/MANIFEST.MF
nmw-oss-parent-1.1.0
Release Links
Release Notes
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:
POST-SNAPSHOT
true
-POST-SNAPSHOT
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.
nmw-oss-parent-1.0.0
Release Links
Release Notes
Project moved to GitHub and Maven.
Set maven-surefire-plugin back to default configuration for better interaction with standard development tools.