META-INF.resources.ao-oss-parent.changelog.jspx Maven / Gradle / Ivy
-
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
.
- Updated plugin versions.
- Updated plugin versions.
-
Switched back to generating Javadocs links with target="_top"
on all versions of
Java. Eventhough the API Docs are generate without frames as of Java 9, they may still be used
within frames in other contexts, such as when viewed at .
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.
- Added default NetBeans server settings.
- Added default NetBeans hint settings.
- Java updates:
- Java 14 is now end-of-life
- Java 15 is now current stable
- Java 16 is new beta
- Updated plugin versions.
- Added default NetBeans formatting settings.
- Added default NetBeans line ending settings.
- Added plugin repositories to match repositories.
-
Now
analyzing dependencies
during release builds.
-
Now automatically configures
rulesUri
for versions-maven-plugin
when the versions-rules.xml
file exists, via a new versions-rules
profile.
- Updated plugin versions.
- Corrected the default value for the Maven build property
documented.javadoc.link.javaee
.
-
Set
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
converted to
on maven-javadoc-plugin , taking
advantage of the new 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
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 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.
-
Added
axis2-aar-maven-plugin for building web services.
- Configured manifest entries consistent with other plugins.
-
Changed
Built-By
manifest entries from defaulting to blank
to now defaulting to \${project.organization.name}
.
-
Enabled
on maven-war-plugin when
src/main/java
exists. This allows the classes to by used as a dependency.
This is particularly useful for our multi-project translation tools.
-
Set
on maven-surefire-plugin .
The full stack traces of exceptions during testing should help in debugging.
-
Defined default compilation 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.
-
Added
tests ,
test-javadoc ,
and test-sources
artifacts, unless empty.
-
Configured
maven-war-plugin to support filtered
META-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 projects
must 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.
-
Newer versions of Javadocs no longer use frames. We now build
API docs with target="_self"
for .
We still support building with older JDK versions,
in which target="_top"
is used so that links
can escape the frames.
- Updated plugin versions.
- Updated links to
- Fixed last release referenced
-SNAPSHOT
version of ao-javadoc-resources
.
- 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.javase
in 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.bootclasspath
into 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
.
- Added build properties for Java EE:
javaee.version
,default 6
javadoc.link.javaee
, default \${javadoc.link.javaee.6}
documented.javaee.version
, default 6
documented.javadoc.link.javaee
, default \${javadoc.link.javaee.6}
-
Added
configuration to maven-javadoc-plugin to build correctly in Java 11.
- Simplified use of
maven-gpg-plugin :
- Changed
lockMode to a fixed value "multiple"
- Removed
defaultKeyring
- Removed
useAgent
- Removed
publicKeyring
- Removed
secretKeyring
- Now using
--release
instead of -bootclasspath
when building with .
- Java updates:
- Java 13 is now end-of-life
- Java 14 is now current stable
- Java 15 is new beta
-
Changed default
doclint
from -Xdoclint:none
to -Xdoclint:all,-missing
.
- Updated plugin versions.
-
To significantly reduce the size of Javadocs, using new
project instead of data:
URLs.
- Java updates:
- Java 12 is now end-of-life
- Java 13 is now current stable
- Java 14 is new beta
- Updated plugin versions.
-
Set delimiters for maven-war-plugin
to match the configuration of maven-resources-plugin ,
using @{*}
.
Also enabled filteringDeploymentDescriptors
by default.
- Updated plugin versions.
-
Changed
Include-Resource
to {maven-resources}, target/resources-filtered
in order to not leak full build paths into META-INF/MANIFEST.MF
- 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:
- Updated parent POM
- Updated POM
- Updated Java version (without any source code changes)
- Updated dependency versions
- Updated javadocs
- Updated documentation
- Updated unit tests
- Deprecated methods and classes
- Renamed private fields and local variables
- 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.
-
No longer including JUnit version in dependencyManagement.
Each project should specify its own JUnit version.
- Set maven-surefire-plugin back to default configuration for better interaction with standard development tools.
-
No longer excluding
Java EE Web API 6
from version updates .
Instead, projects are encouraged to use the new
project.
-
Removed the repository "java.net2" that was going to
.
All the artifacts we require are in The Central Repository .
- Supporting parallel development of projects from unrelated clients:
- Multiple
GPG signing keys .
- Multiple
OSSRH accounts.
Multiple SSH keys for different GitHub accounts.
- Sharing of all these resources with each client for business continuity.
- Updated plugin versions.
-
Added support for packaging as OSGI bundles as
via the Maven Bundle Plugin .
- Now including unfiltered form of
src/main/resources-filtered
in source artifacts.
- Fixed bug:
build.currentYear
property was only available during release builds.
- Now supporting Java 12:
- Changed default Java version from 1.6 to 1.7
- Renamed Maven build property names to not conflict with newer versions of Java:
*.jdk15
→ *.jdk5
*.jdk16
→ *.jdk6
*.jdk17
→ *.jdk7
*.jdk18
→ *.jdk8
-
Fixed cross-project linking of javadocs (really this time).
The issue was our redirects from
*/apidocs/
to */apidocs/index.html
were interacting with a Maven plugin bug:
[MJAVADOC-539] Upgrading plugin from 3.0.0 to 3.0.1 and 3.1.0 breaks certain external javadoc links .
-
Changed minimum Maven version enforcement from
to use the Maven Enforcer Plugin
instead. This eliminates the warnings introduced in
Maven 3.5.0 .
- Updated plugin versions.
-
Added more plugin versions under
build/pluginManagement
to
both support repeatable builds and keep the output of
versions:display-plugin-updates
more meaningful.
- Fixed cross-project linking of javadocs.
- Added
--allow-script-in-comments
for Javadoc in JDK 1.8.0_121+.
- Updated dependencies.
- Added more properties for Java SE javadocs:
javac.link.javaApi.jdk15
for Java 5
javac.link.javaApi.jdk19
for Java 9
- Added properties for Java EE javadocs:
javac.link.javaeeApi.5
for Java EE 5
javac.link.javaeeApi.6
for Java EE 6
javac.link.javaeeApi.7
for Java EE 7
-
javac.link.javaeeApi.8
for Java EE 8.
This is just a link to Java EE overall since the Java EE 8 API has not been released yet.
- Using latest release of plugins.
- Removed erroneous
.
- New parent pom for open-source projects to reduce duplication within pom.xml files
- Made the components of the current version available as
parsedVersion.* properties .
- Using
dependencyversion-maven-plugin to get dependency versions as properties.