Fail Gradle build for Javadoc warnings
In order to catch Javadoc errors in the build, we now enable the `Xwerror` flag for the `javadoc` tool. In addition, we now use `Xdoclint:syntax` instead of `Xdoclint:none` in order to validate syntax within our Javadoc. This commit fixes all resulting Javadoc errors and warnings. This commit also upgrades to Undertow 2.2.12.Final and fixes the artifact names for exclusions for the Servlet and annotations APIs. The incorrect exclusion of the Servlet API resulted in the Servlet API being on the classpath twice for the javadoc task, which resulted in the following warnings in previous builds. javadoc: warning - Multiple sources of package comments found for package "javax.servlet" javadoc: warning - Multiple sources of package comments found for package "javax.servlet.http" javadoc: warning - Multiple sources of package comments found for package "javax.servlet.descriptor" javadoc: warning - Multiple sources of package comments found for package "javax.servlet.annotation" Closes gh-27480
This commit is contained in:
@@ -55,7 +55,7 @@ import org.springframework.util.StringUtils;
|
||||
* <property name="targetConnectionFactory" ref="myTargetConnectionFactory"/>
|
||||
* <property name="username" value="myusername"/>
|
||||
* <property name="password" value="mypassword"/>
|
||||
* </bean></pre>
|
||||
* </bean></pre>
|
||||
*
|
||||
* <p>If the "username" is empty, this proxy will simply delegate to the standard
|
||||
* {@code createConnection()} method of the target ConnectionFactory.
|
||||
|
||||
@@ -33,7 +33,7 @@ import org.springframework.beans.BeanWrapper;
|
||||
* <p>An ActivationSpec factory is effectively dependent on the concrete
|
||||
* JMS provider, e.g. on ActiveMQ. This default implementation simply
|
||||
* guesses the ActivationSpec class name from the provider's class name
|
||||
* ("ActiveMQResourceAdapter" -> "ActiveMQActivationSpec" in the same package,
|
||||
* ("ActiveMQResourceAdapter" → "ActiveMQActivationSpec" in the same package,
|
||||
* or "ActivationSpecImpl" in the same package as the ResourceAdapter class),
|
||||
* and populates the ActivationSpec properties as suggested by the
|
||||
* JCA 1.5 specification (Appendix B). Specify the 'activationSpecClass'
|
||||
@@ -68,7 +68,7 @@ public class DefaultJmsActivationSpecFactory extends StandardJmsActivationSpecFa
|
||||
|
||||
/**
|
||||
* This implementation guesses the ActivationSpec class name from the
|
||||
* provider's class name: e.g. "ActiveMQResourceAdapter" ->
|
||||
* provider's class name: e.g. "ActiveMQResourceAdapter" →
|
||||
* "ActiveMQActivationSpec" in the same package, or a class named
|
||||
* "ActivationSpecImpl" in the same package as the ResourceAdapter class.
|
||||
*/
|
||||
|
||||
@@ -104,7 +104,7 @@ public class JmsMessageEndpointManager extends GenericMessageEndpointManager
|
||||
* {@link #setActivationSpecConfig JmsActivationSpecConfig} objects.
|
||||
* <p>This factory is dependent on the concrete JMS provider, e.g. on ActiveMQ.
|
||||
* The default implementation simply guesses the ActivationSpec class name
|
||||
* from the provider's class name (e.g. "ActiveMQResourceAdapter" ->
|
||||
* from the provider's class name (e.g. "ActiveMQResourceAdapter" →
|
||||
* "ActiveMQActivationSpec" in the same package), and populates the
|
||||
* ActivationSpec properties as suggested by the JCA 1.5 specification
|
||||
* (plus a couple of autodetected vendor-specific properties).
|
||||
|
||||
Reference in New Issue
Block a user