[JBoss JIRA] (ELY-1671) Unable to build javadoc on JDK 10 and JDK 11
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1671?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1671:
-----------------------------
Description:
JDK 10 Error:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.854 s
[INFO] Finished at: 2018-09-19T13:50:48+01:00
[INFO] Final Memory: 26M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
[ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
[ERROR] are planned to be removed in a future JDK release. These
[ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
[ERROR] Users are strongly recommended to migrate to the new APIs.
[ERROR] javadoc: error - invalid flag: -Xdoclint:none
[ERROR]
[ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
JDK 11 Error:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.908 s
[INFO] Finished at: 2018-10-01T10:19:12-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - /home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/src/main/java/org/wildfly/security/manager/JDKSpecific.java:20: error: cannot find symbol
[ERROR] import sun.reflect.Reflection;
[ERROR] ^
[ERROR] symbol: class Reflection
[ERROR] location: package sun.reflect
[ERROR]
[ERROR] Command line was: /home/jucook/JDKs/Java11/OpenJDK/openjdk-11-ea+26_linux-x64_bin/jdk-11/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
was:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.854 s
[INFO] Finished at: 2018-09-19T13:50:48+01:00
[INFO] Final Memory: 26M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
[ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
[ERROR] are planned to be removed in a future JDK release. These
[ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
[ERROR] Users are strongly recommended to migrate to the new APIs.
[ERROR] javadoc: error - invalid flag: -Xdoclint:none
[ERROR]
[ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
> Unable to build javadoc on JDK 10 and JDK 11
> --------------------------------------------
>
> Key: ELY-1671
> URL: https://issues.jboss.org/browse/ELY-1671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Documentation
> Reporter: Darran Lofthouse
> Assignee: Justin Cook
> Priority: Blocker
> Fix For: 1.7.0.CR3
>
>
> JDK 10 Error:
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.854 s
> [INFO] Finished at: 2018-09-19T13:50:48+01:00
> [INFO] Final Memory: 26M/108M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
> [ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
> [ERROR] are planned to be removed in a future JDK release. These
> [ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
> [ERROR] Users are strongly recommended to migrate to the new APIs.
> [ERROR] javadoc: error - invalid flag: -Xdoclint:none
> [ERROR]
> [ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> JDK 11 Error:
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.908 s
> [INFO] Finished at: 2018-10-01T10:19:12-04:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - /home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/src/main/java/org/wildfly/security/manager/JDKSpecific.java:20: error: cannot find symbol
> [ERROR] import sun.reflect.Reflection;
> [ERROR] ^
> [ERROR] symbol: class Reflection
> [ERROR] location: package sun.reflect
> [ERROR]
> [ERROR] Command line was: /home/jucook/JDKs/Java11/OpenJDK/openjdk-11-ea+26_linux-x64_bin/jdk-11/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (ELY-1671) Unable to build javadoc on JDK 10 and JDK 11
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1671?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1671:
-----------------------------
Summary: Unable to build javadoc on JDK 10 and JDK 11 (was: Unable to build javadoc on JDK 10)
> Unable to build javadoc on JDK 10 and JDK 11
> --------------------------------------------
>
> Key: ELY-1671
> URL: https://issues.jboss.org/browse/ELY-1671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Documentation
> Reporter: Darran Lofthouse
> Assignee: Justin Cook
> Priority: Blocker
> Fix For: 1.7.0.CR3
>
>
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.854 s
> [INFO] Finished at: 2018-09-19T13:50:48+01:00
> [INFO] Final Memory: 26M/108M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
> [ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
> [ERROR] are planned to be removed in a future JDK release. These
> [ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
> [ERROR] Users are strongly recommended to migrate to the new APIs.
> [ERROR] javadoc: error - invalid flag: -Xdoclint:none
> [ERROR]
> [ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFLY-10188) Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10188?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10188:
-----------------------------------------
[~swd847] Sorry; I didn't see this. That sounds reasonable, particularly if it was impossible (or at least quite hard) to configure a working server via the CLI in a manner that would now break. Without thinking hard the only way I think that would happen was if CLI scripts were used to recreate our existing standard configuration and the script did not set the attributes.
> Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10188
> URL: https://issues.jboss.org/browse/WFLY-10188
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Pavel Jelinek
> Assignee: Stuart Douglas
> Priority: Critical
>
> Undertow server needs default-host to be set to be able to be used as Undertow subsystem default-server otherwise Wildfly would not start due to:
> {code}
> ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=undertow' are not available:
> org.wildfly.undertow.host.test-server.default-host; Possible registration points for this capability:
> /subsystem=undertow/server=*/host=*
> {code}
> This is dangerous as after calling a {{reload}} operation, the server simply fails and crashes. One can accidentaly kill the server with this and \!manual\! fix is necessary to the configuration to be able to start server again.
> I think that there should be some check that configuration of the newly created server is complete and valid before it is set as a default server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (DROOLS-2952) Hierarhical DataSource
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2952?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-2952:
----------------------------------
Sprint: (was: 2018 Week 39-41)
> Hierarhical DataSource
> ----------------------
>
> Key: DROOLS-2952
> URL: https://issues.jboss.org/browse/DROOLS-2952
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> A really useful addition to DataSources would be scoped hierarchy.
> Lets say I make DataSource d1, and unit u1 is instantiated with it.
> I then want to instantiate d2, where d1 is the parent. I then instantiate u2 with d2.
> That means u2 can seemlessly see and react to all the data in d2 and d1. u1 can only see and react to u1.
> If u2 does inserts, those go into d2.
> If u2 is garbage collected and no references remain on d2, it is also GC'd. This allows a for temporary and local DataSources, scoped to a given unit.
> We can then add control structure methods such as:
> moveAllToParent()
> This would move all the FHs in d2 into d1. We might do this if u2 successfully finishes and d2 is about to be discarded, but we want to keep the results.
> For a given DataSuorce we should be able to determine if it's root, or get it's level. We should always be able to get and insert into root, parent, or any numerically specific level.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months
[JBoss JIRA] (WFLY-10188) Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-10188?page=com.atlassian.jira.plugin... ]
Jan Stourac commented on WFLY-10188:
------------------------------------
This is still issue for WildFly 14.
> Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10188
> URL: https://issues.jboss.org/browse/WFLY-10188
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Pavel Jelinek
> Assignee: Stuart Douglas
> Priority: Critical
>
> Undertow server needs default-host to be set to be able to be used as Undertow subsystem default-server otherwise Wildfly would not start due to:
> {code}
> ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=undertow' are not available:
> org.wildfly.undertow.host.test-server.default-host; Possible registration points for this capability:
> /subsystem=undertow/server=*/host=*
> {code}
> This is dangerous as after calling a {{reload}} operation, the server simply fails and crashes. One can accidentaly kill the server with this and \!manual\! fix is necessary to the configuration to be able to start server again.
> I think that there should be some check that configuration of the newly created server is complete and valid before it is set as a default server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 6 months