[JBoss JIRA] (WFLY-13908) quickstart - wildfly-checkstyle-config update to 1.0.8.Final
by Richard Chan (Jira)
[ https://issues.redhat.com/browse/WFLY-13908?page=com.atlassian.jira.plugi... ]
Richard Chan updated WFLY-13908:
--------------------------------
Description:
Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
Summary:
* pom.xml works in maven CLI
* Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
Forcing command line to use 1.0.7.Final + checkstyle 8.35:
{code:java}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project helloworld: An error has occurred in Checkstyle report generation.: Failed during checkstyle configuration: cannot initialize module TreeWalker - Property 'cacheFile' does not exist, please check the documentation -> [Help 1]
{code}
was:
Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
Summary:
* pom.xml works in maven CLI
* Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
Forcing command line to use 1.0.7.Final + checkstyle 8.35:
{{}}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project helloworld: An error has occurred in Checkstyle report generation.: Failed during checkstyle configuration: cannot initialize module TreeWalker - Property 'cacheFile' does not exist, please check the documentation -> [Help 1]
> quickstart - wildfly-checkstyle-config update to 1.0.8.Final
> ------------------------------------------------------------
>
> Key: WFLY-13908
> URL: https://issues.redhat.com/browse/WFLY-13908
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Chan
> Assignee: Eduardo Martins
> Priority: Trivial
>
> Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
> This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
>
> Summary:
> * pom.xml works in maven CLI
> * Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
>
> Forcing command line to use 1.0.7.Final + checkstyle 8.35:
> {code:java}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project helloworld: An error has occurred in Checkstyle report generation.: Failed during checkstyle configuration: cannot initialize module TreeWalker - Property 'cacheFile' does not exist, please check the documentation -> [Help 1]
> {code}
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13908) quickstart - wildfly-checkstyle-config update to 1.0.8.Final
by Richard Chan (Jira)
[ https://issues.redhat.com/browse/WFLY-13908?page=com.atlassian.jira.plugi... ]
Richard Chan updated WFLY-13908:
--------------------------------
Description:
Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
Summary:
* pom.xml works in maven CLI
* Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
Forcing command line to use 1.0.7.Final + checkstyle 8.35:
{{}}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project helloworld: An error has occurred in Checkstyle report generation.: Failed during checkstyle configuration: cannot initialize module TreeWalker - Property 'cacheFile' does not exist, please check the documentation -> [Help 1]
was:
Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
Summary:
* pom.xml works in maven CLI
* Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
> quickstart - wildfly-checkstyle-config update to 1.0.8.Final
> ------------------------------------------------------------
>
> Key: WFLY-13908
> URL: https://issues.redhat.com/browse/WFLY-13908
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Chan
> Assignee: Eduardo Martins
> Priority: Trivial
>
> Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
> This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
>
> Summary:
> * pom.xml works in maven CLI
> * Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
>
> Forcing command line to use 1.0.7.Final + checkstyle 8.35:
> {{}}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:checkstyle (default-cli) on project helloworld: An error has occurred in Checkstyle report generation.: Failed during checkstyle configuration: cannot initialize module TreeWalker - Property 'cacheFile' does not exist, please check the documentation -> [Help 1]
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13908) quickstart - wildfly-checkstyle-config update to 1.0.8.Final
by Richard Chan (Jira)
[ https://issues.redhat.com/browse/WFLY-13908?page=com.atlassian.jira.plugi... ]
Richard Chan updated WFLY-13908:
--------------------------------
Steps to Reproduce:
# Download quickstarts 20.0.1.Final
# Import helloworld into Eclipse and use m2e mapping for checkstyle
# Observe: in shell, mvn clean checkstyle:checkstyle should succeed
# Build project in Eclipse: observe checkstyle error
was:
# Download quickstarts 20.0.1.Final
# Import helloworld into Eclipse and use m2e mapping for checkstyle
# Observe: in shell, mvn clean checkstyle:checkstyle should succeed
# Build project in Eclipse
> quickstart - wildfly-checkstyle-config update to 1.0.8.Final
> ------------------------------------------------------------
>
> Key: WFLY-13908
> URL: https://issues.redhat.com/browse/WFLY-13908
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Chan
> Assignee: Eduardo Martins
> Priority: Trivial
>
> Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
> This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
>
> Summary:
> * pom.xml works in maven CLI
> * Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13908) quickstart - wildfly-checkstyle-config update to 1.0.8.Final
by Richard Chan (Jira)
[ https://issues.redhat.com/browse/WFLY-13908?page=com.atlassian.jira.plugi... ]
Richard Chan updated WFLY-13908:
--------------------------------
Summary: quickstart - wildfly-checkstyle-config update to 1.0.8.Final (was: quckstart - wildfly-checkstyle-config update to 1.0.8.Final)
> quickstart - wildfly-checkstyle-config update to 1.0.8.Final
> ------------------------------------------------------------
>
> Key: WFLY-13908
> URL: https://issues.redhat.com/browse/WFLY-13908
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Chan
> Assignee: Eduardo Martins
> Priority: Trivial
>
> Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
> This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
>
> Summary:
> * pom.xml works in maven CLI
> * Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13908) quckstart - wildfly-checkstyle-config update to 1.0.8.Final
by Richard Chan (Jira)
Richard Chan created WFLY-13908:
-----------------------------------
Summary: quckstart - wildfly-checkstyle-config update to 1.0.8.Final
Key: WFLY-13908
URL: https://issues.redhat.com/browse/WFLY-13908
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Affects Versions: 21.0.0.Beta1
Reporter: Richard Chan
Assignee: Eduardo Martins
Eclipse m2e mapping for checkstyle uses version 8.35 (non-configurable - vs 8.5 in pom.xml). As a result, running inside Eclipse has the error (with any checkstyle >= 8.19): TreeWalker has no cacheFile property.
This checkstyle config was updated in wildfly-config-checkstyle 1.0.8.Final to be >= 8.19 compatible.
Summary:
* pom.xml works in maven CLI
* Importing into Eclipse does not work cleanly, due to error messages from newer checkstyle 8.35 and wildfly-checkstyle-config 1.0.7.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ]
James Perkins commented on WFCORE-4674:
---------------------------------------
[~francisco.melojr] Sure.
# The first step is to replace the jboss-modules.jar.
# Next you'd need to change the standalone script file you want to use. See https://github.com/wildfly/wildfly-core/pull/4131/files#diff-20ab07589c7e...
# Then you can updated your {{standalone.conf}} file.
Note the PR has all the details https://github.com/wildfly/wildfly-core/pull/4131/. If you want it to work for domain servers there is a lot more work involved.
> Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4674
> URL: https://issues.redhat.com/browse/WFCORE-4674
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Critical
> Labels: OpenShift, jdk11
> Fix For: 13.0.0.Beta1
>
>
> If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path.
> Example exception:
> {code}
> Failed to read or configure the org.jboss.logmanager.LogManager
> java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON"
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65)
> at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172)
> at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631)
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701)
> at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
> at java.util.logging.LogManager$3.run(LogManager.java:399)
> at java.util.logging.LogManager$3.run(LogManager.java:396)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
> at java.util.logging.LogManager.access$800(LogManager.java:145)
> at java.util.logging.LogManager$2.run(LogManager.java:345)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
> at java.util.logging.LogManager.getLogManager(LogManager.java:378)
> at org.jboss.modules.Main.main(Main.java:523)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556)
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63)
> ... 19 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
by Francisco De Melo Junior (Jira)
[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ]
Francisco De Melo Junior commented on WFCORE-4674:
--------------------------------------------------
[~jamezp] since we are already here, could you describe the steps. I sincerely thought replacing the modules and changing standalone.conf was enough.
> Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4674
> URL: https://issues.redhat.com/browse/WFCORE-4674
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Critical
> Labels: OpenShift, jdk11
> Fix For: 13.0.0.Beta1
>
>
> If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path.
> Example exception:
> {code}
> Failed to read or configure the org.jboss.logmanager.LogManager
> java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON"
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65)
> at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172)
> at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631)
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701)
> at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
> at java.util.logging.LogManager$3.run(LogManager.java:399)
> at java.util.logging.LogManager$3.run(LogManager.java:396)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
> at java.util.logging.LogManager.access$800(LogManager.java:145)
> at java.util.logging.LogManager$2.run(LogManager.java:345)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
> at java.util.logging.LogManager.getLogManager(LogManager.java:378)
> at org.jboss.modules.Main.main(Main.java:523)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556)
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63)
> ... 19 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months