[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ]
Erich Duda updated WFWIP-90:
----------------------------
Component/s: Clustering
> [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart
> -------------------------------------------------------------------------------
>
> Key: WFWIP-90
> URL: https://issues.jboss.org/browse/WFWIP-90
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, Clustering
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
>
> There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test.
> Test scenario:
> * Start 2 server in Artemis cluster
> * Start 2 servers with MDB connected to Artemis cluster
> ** MDB resends messages from InQueue to OutQueue from/to remote cluster
> * Send messages to InQueue
> * Restart all server (one by one)
> * Consumes messages from OutQueue
> Results:
> After the test there are missing messages in OutQueue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10841) XA recovery warnings when server reloaded
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10841?page=com.atlassian.jira.plugin... ]
Ondra Chaloupka reassigned WFLY-10841:
--------------------------------------
Assignee: Ondra Chaloupka (was: Jeff Mesnil)
> XA recovery warnings when server reloaded
> -----------------------------------------
>
> Key: WFLY-10841
> URL: https://issues.jboss.org/browse/WFLY-10841
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Transactions
> Affects Versions: 13.0.0.Final
> Reporter: Chao Wang
> Assignee: Ondra Chaloupka
>
> Following warning messages are outputted when server reloaded.
> {code}
> 15:33:52,740 WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ122015: Can not connect to XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemi
> s-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryConfiguration=null, username=null, password=****, JNDI_NAME=java:/JmsXA] on auto-generated resource recovery: ActiveMQNotConnectedException[errorType=NOT_CONNECTED m
> essage=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787)
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.connect(ActiveMQXAResourceWrapper.java:311)
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:239)
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.recover(ActiveMQXAResourceWrapper.java:69)
> at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.recover(ActiveMQXAResourceWrapperImpl.java:106)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:791)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:482)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:233)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:150)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:140)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377)
> 15:33:52,752 WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ122008: XA Recovery can not connect to any broker on recovery [XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=
> , factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryConfiguration=null, username=null, password=****, JNDI_NAME=java:/JmsXA]]
> 15:33:52,752 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMFAIL: javax.transaction.xa.XAException: Error trying to connect to any providers for xa reco
> very
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:258)
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.recover(ActiveMQXAResourceWrapper.java:69)
> at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.recover(ActiveMQXAResourceWrapperImpl.java:106)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:791)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:482)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:233)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:150)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:140)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377)
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=null]
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.connect(ActiveMQXAResourceWrapper.java:345)
> at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:239)
> ... 9 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ]
Jan Kalina commented on ELY-1639:
---------------------------------
Agree - sorry, my impl has not considered there are other types of entries in keystore, however it is also true it is usually KeyManager's responsibility to choose one of keys from the keystore and there is no reason to keep such check in place - removing.
> FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used
> -------------------------------------------------------------
>
> Key: ELY-1639
> URL: https://issues.jboss.org/browse/ELY-1639
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Blocker
> Attachments: cli-wildfly-config.xml
>
>
> Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception
> {code}
> 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost'
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: Failed to obtain SSLContext
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> ... 8 more
> Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used
> at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149)
> at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66)
> at javax.net.ssl.SSLContext.init(SSLContext.java:282)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153)
> ... 10 more
> {code}
> It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFCORE-4048) Unable to configure custom security realm in deployment
by Martin Švehla (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4048?page=com.atlassian.jira.plugi... ]
Martin Švehla commented on WFCORE-4048:
---------------------------------------
Won't this be solved by adding JASPIC capabilities to Elytron? User can add their SAM in deployment which in turn should be able to do what their login module used to do.
> Unable to configure custom security realm in deployment
> -------------------------------------------------------
>
> Key: WFCORE-4048
> URL: https://issues.jboss.org/browse/WFCORE-4048
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 6.0.0.CR2
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
>
> Original user report [1]:
> Hello everyone, I am migrating from legacy security to Elytron, and I have a problem. Is there anyone who can help me? We have a custom login-module that queries infinispan cache (which maps simple bearer tokens to user names), and then queries the database (to get user roles), and on commit essentially wraps it up in Principal object. Elytron doesn't have login-modules, but security realms. There is no default realm that matches our desired functionality, so we need to define a new custom-realm. The problem is, security realms can be defined with classes in wildfly "modules", not deployments. And since "modules" can't contain EJB's, I can't inject neither infinispan cache nor database entity manager in the code. Please help what is the right way to go here
> I was thinking about it and I have come to conclusion that Elytron is not able to do the same as legacy. I assume that user is right that you cant use EE features in modules. And it looks to me Elytorn does not allow dependency on deployment module. Because Elytron checks existance of module in time of starting and deployment can be not loaded yet. In legacy existance verification is apparently postponed to time of usage.
> So I assume in legacy you can define custom login module in deployment (with EE annotations) and register such login module in security subsystem. And dependencies are resolved in runtime and not in boottime.
> [1] https://wildfly.hipchat.com/embedded/history/room/699248/2018/07/18?p=1&q...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10861) MP Health - security enabled, no user yed added, user get info about adding user to access management interface, HTTP code is 200, should be 500
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10861?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda updated WFLY-10861:
-------------------------------------
Description:
I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server
Note: I didn't add user via {{bin/add-user.sh}}
----
Kabir edit: the full command is:
/subsystem=microprofile-health-smallrye:write-attribute(name=security-enabled,value=true)
----
When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console:
{code}
<h3>Your WildFly Application Server is running.</h3>
<p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able
to access the admin console.</p>
<p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of
your WildFly installation and enter the requested information.</p>
{code}
Can /health endpoint get customized response in case no mgmt user is defined on server side ?
Current response can be little confusing if user is not yet so familiar with WildFly.
-I marked this as minor bug.- ... see comments
was:
I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server
Note: I didn't add user via {{bin/add-user.sh}}
----
Kabir edit: the full command is:
/subsystem=microprofile-health-smallrye:write-attribute(name=security-enabled,value=true)
----
When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console:
{code}
<h3>Your WildFly Application Server is running.</h3>
<p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able
to access the admin console.</p>
<p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of
your WildFly installation and enter the requested information.</p>
{code}
Can /health endpoint get customized response in case no mgmt user is defined on server side ?
Current response can be little confusing if user is not yet so familiar with WildFly.
I marked this as minor bug.
> MP Health - security enabled, no user yed added, user get info about adding user to access management interface, HTTP code is 200, should be 500
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10861
> URL: https://issues.jboss.org/browse/WFLY-10861
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Health
> Reporter: Rostislav Svoboda
> Assignee: Kabir Khan
> Priority: Blocker
>
> I do {{:write-attribute(name=security-enabled, value=true)}} ++ reload of the server
> Note: I didn't add user via {{bin/add-user.sh}}
> ----
> Kabir edit: the full command is:
> /subsystem=microprofile-health-smallrye:write-attribute(name=security-enabled,value=true)
> ----
> When I'm trying to access http://127.0.0.1:9990/health I receive page which is there primarily for web console:
> {code}
> <h3>Your WildFly Application Server is running.</h3>
> <p>However you have <strong>not</strong> yet <strong>added any users</strong> to be able
> to access the admin console.</p>
> <p>To add a new user execute the <code>add-user.sh</code> script within the bin folder of
> your WildFly installation and enter the requested information.</p>
> {code}
> Can /health endpoint get customized response in case no mgmt user is defined on server side ?
> Current response can be little confusing if user is not yet so familiar with WildFly.
> -I marked this as minor bug.- ... see comments
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2896) Turn On Code Static Analysis for kie-wb-common repository
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2896?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2896:
--------------------------------
Component/s: (was: Guided Decision Table Editor)
(was: Guided Decision Tree Editor)
(was: Guided Rule Editor)
(was: Guided Score Card Editor)
(was: Guided Template Editor)
(was: Test Scenarios Editor)
(was: XLS Decision Table Editor)
> Turn On Code Static Analysis for kie-wb-common repository
> ---------------------------------------------------------
>
> Key: DROOLS-2896
> URL: https://issues.jboss.org/browse/DROOLS-2896
> Project: Drools
> Issue Type: Task
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.5.0.Final
>
>
> Add the configuration below to the pom.xml and make sure all modules of drools-wb repository are passing the build.
> {code:xml}
> <checkstyle.header.template><![CDATA[
> ^\/\*$\n^
> \* Copyright \d\d\d\d Red Hat, Inc\. and\/or its affiliates\.$\n^
> \*$\n^
> \* Licensed under the Apache License, Version 2\.0 \(the "License"\);$\n^
> \* you may not use this file except in compliance with the License\.$\n^
> \* You may obtain a copy of the License at$\n^
> \*$\n^
> \* http:\/\/www\.apache\.org\/licenses\/LICENSE-2\.0$\n^
> \*$\n^
> \* Unless required by applicable law or agreed to in writing, software$\n^
> \* distributed under the License is distributed on an "AS IS" BASIS,$\n^
> \* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied\.$\n^
> \* See the License for the specific language governing permissions and$\n^
> \* limitations under the License\.$\n^
> \*\/$
> ]]>
> </checkstyle.header.template>
> <checkstyle.failOnViolation>true</checkstyle.failOnViolation>
> <checkstyle.logViolationsToConsole>true</checkstyle.logViolationsToConsole>
> <jacoco.haltOnFailure>true</jacoco.haltOnFailure>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2896) Turn On Code Static Analysis for kie-wb-common repository
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2896?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2896:
--------------------------------
Git Pull Request: (was: https://github.com/kiegroup/drools-wb/pull/696)
> Turn On Code Static Analysis for kie-wb-common repository
> ---------------------------------------------------------
>
> Key: DROOLS-2896
> URL: https://issues.jboss.org/browse/DROOLS-2896
> Project: Drools
> Issue Type: Task
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.5.0.Final
>
>
> Add the configuration below to the pom.xml and make sure all modules of drools-wb repository are passing the build.
> {code:xml}
> <checkstyle.header.template><![CDATA[
> ^\/\*$\n^
> \* Copyright \d\d\d\d Red Hat, Inc\. and\/or its affiliates\.$\n^
> \*$\n^
> \* Licensed under the Apache License, Version 2\.0 \(the "License"\);$\n^
> \* you may not use this file except in compliance with the License\.$\n^
> \* You may obtain a copy of the License at$\n^
> \*$\n^
> \* http:\/\/www\.apache\.org\/licenses\/LICENSE-2\.0$\n^
> \*$\n^
> \* Unless required by applicable law or agreed to in writing, software$\n^
> \* distributed under the License is distributed on an "AS IS" BASIS,$\n^
> \* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied\.$\n^
> \* See the License for the specific language governing permissions and$\n^
> \* limitations under the License\.$\n^
> \*\/$
> ]]>
> </checkstyle.header.template>
> <checkstyle.failOnViolation>true</checkstyle.failOnViolation>
> <checkstyle.logViolationsToConsole>true</checkstyle.logViolationsToConsole>
> <jacoco.haltOnFailure>true</jacoco.haltOnFailure>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2896) Turn On Code Static Analysis for kie-wb-common repository
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2896:
-----------------------------------
Summary: Turn On Code Static Analysis for kie-wb-common repository
Key: DROOLS-2896
URL: https://issues.jboss.org/browse/DROOLS-2896
Project: Drools
Issue Type: Task
Components: Guided Decision Table Editor, Guided Decision Tree Editor, Guided Rule Editor, Guided Score Card Editor, Guided Template Editor, Test Scenarios Editor, XLS Decision Table Editor
Affects Versions: 7.4.1.Final
Reporter: Jozef Marko
Assignee: Jozef Marko
Fix For: 7.5.0.Final
Add the configuration below to the pom.xml and make sure all modules of drools-wb repository are passing the build.
{code:xml}
<checkstyle.header.template><![CDATA[
^\/\*$\n^
\* Copyright \d\d\d\d Red Hat, Inc\. and\/or its affiliates\.$\n^
\*$\n^
\* Licensed under the Apache License, Version 2\.0 \(the "License"\);$\n^
\* you may not use this file except in compliance with the License\.$\n^
\* You may obtain a copy of the License at$\n^
\*$\n^
\* http:\/\/www\.apache\.org\/licenses\/LICENSE-2\.0$\n^
\*$\n^
\* Unless required by applicable law or agreed to in writing, software$\n^
\* distributed under the License is distributed on an "AS IS" BASIS,$\n^
\* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied\.$\n^
\* See the License for the specific language governing permissions and$\n^
\* limitations under the License\.$\n^
\*\/$
]]>
</checkstyle.header.template>
<checkstyle.failOnViolation>true</checkstyle.failOnViolation>
<checkstyle.logViolationsToConsole>true</checkstyle.logViolationsToConsole>
<jacoco.haltOnFailure>true</jacoco.haltOnFailure>
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2896) Turn On Code Static Analysis for kie-wb-common repository
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2896?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2896:
--------------------------------
Affects Version/s: 7.10.0.Final
(was: 7.4.1.Final)
> Turn On Code Static Analysis for kie-wb-common repository
> ---------------------------------------------------------
>
> Key: DROOLS-2896
> URL: https://issues.jboss.org/browse/DROOLS-2896
> Project: Drools
> Issue Type: Task
> Components: Guided Decision Table Editor, Guided Decision Tree Editor, Guided Rule Editor, Guided Score Card Editor, Guided Template Editor, Test Scenarios Editor, XLS Decision Table Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.5.0.Final
>
>
> Add the configuration below to the pom.xml and make sure all modules of drools-wb repository are passing the build.
> {code:xml}
> <checkstyle.header.template><![CDATA[
> ^\/\*$\n^
> \* Copyright \d\d\d\d Red Hat, Inc\. and\/or its affiliates\.$\n^
> \*$\n^
> \* Licensed under the Apache License, Version 2\.0 \(the "License"\);$\n^
> \* you may not use this file except in compliance with the License\.$\n^
> \* You may obtain a copy of the License at$\n^
> \*$\n^
> \* http:\/\/www\.apache\.org\/licenses\/LICENSE-2\.0$\n^
> \*$\n^
> \* Unless required by applicable law or agreed to in writing, software$\n^
> \* distributed under the License is distributed on an "AS IS" BASIS,$\n^
> \* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied\.$\n^
> \* See the License for the specific language governing permissions and$\n^
> \* limitations under the License\.$\n^
> \*\/$
> ]]>
> </checkstyle.header.template>
> <checkstyle.failOnViolation>true</checkstyle.failOnViolation>
> <checkstyle.logViolationsToConsole>true</checkstyle.logViolationsToConsole>
> <jacoco.haltOnFailure>true</jacoco.haltOnFailure>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months