[JBoss JIRA] (DROOLS-968) Random Nullpointer
by Marko Talijanac (JIRA)
[ https://issues.jboss.org/browse/DROOLS-968?page=com.atlassian.jira.plugin... ]
Marko Talijanac edited comment on DROOLS-968 at 1/25/17 7:07 AM:
-----------------------------------------------------------------
I believe this bug is caused by running drools under IBM J9 JDK. If you follow stack, NullPointerException is caused by class name being null. Reloading drools under same classloader fixes NullPointerException. It seems to me that it is caused by some timing issue under J9 classloader where class name defaults to null for some brief period of time.
I can reproduce this behavior in two seperate enivronments:
- 1. on AIX running WebSphere App Server v8 on AIX with java version:
{noformat}
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr8fp15ifix-20151124_01(SR8 FP15+IV79094))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20151019_272772 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR8_20151019_2248_B272772
JIT - tr.r11_20151005_102425.01
GC - R26_Java626_SR8_20151019_2248_B272772_CMPRSS
J9CL - 20151019_272772)
JCL - 20151105_01
{noformat}
- 2. On Windows 7, running Tomcat v7 with IBM SDK
{noformat}
java version "1.7.0"
Java(TM) SE Runtime Environment (build pwi3270sr1-20120405_01(SR1))
IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20120322_106209 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR1_20120322_1720_B106209
JIT - r11_20120322_22976
GC - R26_Java726_SR1_20120322_1720_B106209
J9CL - 20120322_106209)
JCL - 20120322_01 based on Oracle 7u3-b05
{noformat}
Same tomcat running the oracle jdk doesn't produce the bug. Unfortunatly this issue prevents us from upgrading drools to 5.6.0.Final.
Example:
{noformat}
2017-01-19 16:14:05,011 ERROR [LMSI2-1-7] (LynxManagementServiceImpl2.java:522) - Error starting rule engine for lnet: 'SVK2'
java.lang.NullPointerException
at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:78)
at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:74)
at hr.ispcard.lynx.model.rule.RuleEngine.createKnowledgeBaseFromDRL(RuleEngine.java:162)
at hr.ispcard.lynx.scoring.ScorecardManagerImpl.loadScorecardRuleEngine(ScorecardManagerImpl.java:355)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:505)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:498)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:790)
{noformat}
was (Author: mtalijanac):
I believe this bug is caused by running drools under IBM J9 JDK. If you follow stack, NullPointerException is caused by class name being null. Reloading drools under same classloader fixes NullPointerException. It seems to me that it is caused by some timing issue under J9 classloader where class name defaults to null for some brief period of time.
I can reproduce this behavior in two seperate enivronments:
1. on AIX running WebSphere App Server v8 on AIX with java version:
{noformat}
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr8fp15ifix-20151124_01(SR8 FP15+IV79094))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20151019_272772 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR8_20151019_2248_B272772
JIT - tr.r11_20151005_102425.01
GC - R26_Java626_SR8_20151019_2248_B272772_CMPRSS
J9CL - 20151019_272772)
JCL - 20151105_01
{noformat}
2. On Windows 7, running Tomcat v7 with IBM SDK
{noformat}
java version "1.7.0"
Java(TM) SE Runtime Environment (build pwi3270sr1-20120405_01(SR1))
IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20120322_106209 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR1_20120322_1720_B106209
JIT - r11_20120322_22976
GC - R26_Java726_SR1_20120322_1720_B106209
J9CL - 20120322_106209)
JCL - 20120322_01 based on Oracle 7u3-b05
{noformat}
Same tomcat running the oracle jdk doesn't produce the bug. Unfortunatly this issue prevents us from upgrading drools to 5.6.0.Final.
Example:
{noformat}
2017-01-19 16:14:05,011 ERROR [LMSI2-1-7] (LynxManagementServiceImpl2.java:522) - Error starting rule engine for lnet: 'SVK2'
java.lang.NullPointerException
at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:78)
at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:74)
at hr.ispcard.lynx.model.rule.RuleEngine.createKnowledgeBaseFromDRL(RuleEngine.java:162)
at hr.ispcard.lynx.scoring.ScorecardManagerImpl.loadScorecardRuleEngine(ScorecardManagerImpl.java:355)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:505)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:498)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:790)
{noformat}
> Random Nullpointer
> ------------------
>
> Key: DROOLS-968
> URL: https://issues.jboss.org/browse/DROOLS-968
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final
> Environment: Windows, Jetty
> Reporter: Michal Letynski
> Assignee: Mark Proctor
>
> From time to time i.m getting weird Nullpointer exception. I didn't reproduce the problem when the app is deployed on Glassfish. Only on jetty and only on windows system (with MAC OS everything is ok)
> Stacktrace:
> java.lang.NullPointerException
> at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
> at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:77)
> at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
> at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
> at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
> at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:308)
> at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:236)
> And my code is a simple object creation:
> PackageBuilder packageBuilder = new PackageBuilder();
> Any hint why this might occur ? Or should i just ignore it because on production we have Glassfish server ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-968) Random Nullpointer
by Marko Talijanac (JIRA)
[ https://issues.jboss.org/browse/DROOLS-968?page=com.atlassian.jira.plugin... ]
Marko Talijanac edited comment on DROOLS-968 at 1/25/17 7:06 AM:
-----------------------------------------------------------------
I believe this bug is caused by running drools under IBM J9 JDK. If you follow stack, NullPointerException is caused by class name being null. Reloading drools under same classloader fixes NullPointerException. It seems to me that it is caused by some timing issue under J9 classloader where class name defaults to null for some brief period of time.
I can reproduce this behavior in two seperate enivronments:
1. on AIX running WebSphere App Server v8 on AIX with java version:
{noformat}
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr8fp15ifix-20151124_01(SR8 FP15+IV79094))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20151019_272772 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR8_20151019_2248_B272772
JIT - tr.r11_20151005_102425.01
GC - R26_Java626_SR8_20151019_2248_B272772_CMPRSS
J9CL - 20151019_272772)
JCL - 20151105_01
{noformat}
2. On Windows 7, running Tomcat v7 with IBM SDK
{noformat}
java version "1.7.0"
Java(TM) SE Runtime Environment (build pwi3270sr1-20120405_01(SR1))
IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20120322_106209 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR1_20120322_1720_B106209
JIT - r11_20120322_22976
GC - R26_Java726_SR1_20120322_1720_B106209
J9CL - 20120322_106209)
JCL - 20120322_01 based on Oracle 7u3-b05
{noformat}
Same tomcat running the oracle jdk doesn't produce the bug. Unfortunatly this issue prevents us from upgrading drools to 5.6.0.Final.
Example:
{noformat}
2017-01-19 16:14:05,011 ERROR [LMSI2-1-7] (LynxManagementServiceImpl2.java:522) - Error starting rule engine for lnet: 'SVK2'
java.lang.NullPointerException
at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:78)
at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:74)
at hr.ispcard.lynx.model.rule.RuleEngine.createKnowledgeBaseFromDRL(RuleEngine.java:162)
at hr.ispcard.lynx.scoring.ScorecardManagerImpl.loadScorecardRuleEngine(ScorecardManagerImpl.java:355)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:505)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:498)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:790)
{noformat}
was (Author: mtalijanac):
I believe this bug is caused by running drools under IBM J9 JDK. If you follow stack, NullPointerException is caused by class name being null. Reloading drools under same classloader fixes NullPointerException. It seems to me that it is caused by some timing issue under J9 classloader where class name defaults to null for some brief period of time.
I can reproduce this behavior in two seperate enivronments:
# on AIX running WebSphere App Server v8 on AIX with java version:
{noformat}
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr8fp15ifix-20151124_01(SR8 FP15+IV79094))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20151019_272772 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR8_20151019_2248_B272772
JIT - tr.r11_20151005_102425.01
GC - R26_Java626_SR8_20151019_2248_B272772_CMPRSS
J9CL - 20151019_272772)
JCL - 20151105_01
{noformat}
# On Windows 7, running Tomcat v7 with IBM SDK
{noformat}
java version "1.7.0"
Java(TM) SE Runtime Environment (build pwi3270sr1-20120405_01(SR1))
IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20120322_106209 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR1_20120322_1720_B106209
JIT - r11_20120322_22976
GC - R26_Java726_SR1_20120322_1720_B106209
J9CL - 20120322_106209)
JCL - 20120322_01 based on Oracle 7u3-b05
{noformat}
Same tomcat running the oracle jdk doesn't produce the bug. Unfortunatly this issue prevents us from upgrading drools to 5.6.0.Final.
Example:
{noformat}
2017-01-19 16:14:05,011 ERROR [LMSI2-1-7] (LynxManagementServiceImpl2.java:522) - Error starting rule engine for lnet: 'SVK2'
java.lang.NullPointerException
at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:78)
at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:74)
at hr.ispcard.lynx.model.rule.RuleEngine.createKnowledgeBaseFromDRL(RuleEngine.java:162)
at hr.ispcard.lynx.scoring.ScorecardManagerImpl.loadScorecardRuleEngine(ScorecardManagerImpl.java:355)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:505)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:498)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:790)
{noformat}
> Random Nullpointer
> ------------------
>
> Key: DROOLS-968
> URL: https://issues.jboss.org/browse/DROOLS-968
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final
> Environment: Windows, Jetty
> Reporter: Michal Letynski
> Assignee: Mark Proctor
>
> From time to time i.m getting weird Nullpointer exception. I didn't reproduce the problem when the app is deployed on Glassfish. Only on jetty and only on windows system (with MAC OS everything is ok)
> Stacktrace:
> java.lang.NullPointerException
> at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
> at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:77)
> at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
> at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
> at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
> at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:308)
> at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:236)
> And my code is a simple object creation:
> PackageBuilder packageBuilder = new PackageBuilder();
> Any hint why this might occur ? Or should i just ignore it because on production we have Glassfish server ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-968) Random Nullpointer
by Marko Talijanac (JIRA)
[ https://issues.jboss.org/browse/DROOLS-968?page=com.atlassian.jira.plugin... ]
Marko Talijanac commented on DROOLS-968:
----------------------------------------
I believe this bug is caused by running drools under IBM J9 JDK. If you follow stack, NullPointerException is caused by class name being null. Reloading drools under same classloader fixes NullPointerException. It seems to me that it is caused by some timing issue under J9 classloader where class name defaults to null for some brief period of time.
I can reproduce this behavior in two seperate enivronments:
# on AIX running WebSphere App Server v8 on AIX with java version:
{noformat}
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460_26sr8fp15ifix-20151124_01(SR8 FP15+IV79094))
IBM J9 VM (build 2.6, JRE 1.6.0 AIX ppc64-64 Compressed References 20151019_272772 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR8_20151019_2248_B272772
JIT - tr.r11_20151005_102425.01
GC - R26_Java626_SR8_20151019_2248_B272772_CMPRSS
J9CL - 20151019_272772)
JCL - 20151105_01
{noformat}
# On Windows 7, running Tomcat v7 with IBM SDK
{noformat}
java version "1.7.0"
Java(TM) SE Runtime Environment (build pwi3270sr1-20120405_01(SR1))
IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20120322_106209 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR1_20120322_1720_B106209
JIT - r11_20120322_22976
GC - R26_Java726_SR1_20120322_1720_B106209
J9CL - 20120322_106209)
JCL - 20120322_01 based on Oracle 7u3-b05
{noformat}
Same tomcat running the oracle jdk doesn't produce the bug. Unfortunatly this issue prevents us from upgrading drools to 5.6.0.Final.
Example:
{noformat}
2017-01-19 16:14:05,011 ERROR [LMSI2-1-7] (LynxManagementServiceImpl2.java:522) - Error starting rule engine for lnet: 'SVK2'
java.lang.NullPointerException
at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:78)
at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:74)
at hr.ispcard.lynx.model.rule.RuleEngine.createKnowledgeBaseFromDRL(RuleEngine.java:162)
at hr.ispcard.lynx.scoring.ScorecardManagerImpl.loadScorecardRuleEngine(ScorecardManagerImpl.java:355)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:505)
at hr.ispcard.lynx.service.LynxManagementServiceImpl2$9.call(LynxManagementServiceImpl2.java:498)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:790)
{noformat}
> Random Nullpointer
> ------------------
>
> Key: DROOLS-968
> URL: https://issues.jboss.org/browse/DROOLS-968
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final
> Environment: Windows, Jetty
> Reporter: Michal Letynski
> Assignee: Mark Proctor
>
> From time to time i.m getting weird Nullpointer exception. I didn't reproduce the problem when the app is deployed on Glassfish. Only on jetty and only on windows system (with MAC OS everything is ok)
> Stacktrace:
> java.lang.NullPointerException
> at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
> at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:77)
> at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
> at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
> at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
> at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:308)
> at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:236)
> And my code is a simple object creation:
> PackageBuilder packageBuilder = new PackageBuilder();
> Any hint why this might occur ? Or should i just ignore it because on production we have Glassfish server ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-764) Delete the dependency to commons-lang 2 in all poms in Drools and jBPM (use commons-lang 3 instead)
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-764?page=com.atlassian.jira.plugin... ]
Petr Široký commented on DROOLS-764:
------------------------------------
I am not exactly up-to-date with this issue, but we definitely need to fix the imports as well when changing the dependency. So {{org.apache.commons.lang.text.StrLookup}} -> {{org.apache.commons.lang3.text.StrLookup}}
> Delete the dependency to commons-lang 2 in all poms in Drools and jBPM (use commons-lang 3 instead)
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-764
> URL: https://issues.jboss.org/browse/DROOLS-764
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Minor
>
> Make an inventory of all modules that still use commons-lang and ask their owners to replace the commons-lang 2 usage with commons-lang 3.
> See recipe below how they can quickly do that.
> Once all our modules are upgraded, see if we can remove the commons-lang 2 dependency as much as possible (including the ip-bom hopefully).
> {code}
> Currently we have commons-lang 2.6 and 3.1 in our classpath
> (which is not a problem because they use a different package namespace).
> Nevertheless, having it twice doesn't look good
> and 2.6 might miss security fixes.
> Luckily upgrading is easy (it took me 15 minutes for optaplanner):
> 1) Replace:
> <dependency>
> <groupId>commons-lang</groupId>
> <artifactId>commons-lang</artifactId>
> </dependency>
> with
> <dependency>
> <groupId>org.apache.commons</groupId>
> <artifactId>commons-lang3</artifactId>
> </dependency>
> (Both are already in the ip-bom, so no need to worry about <version>)
> 2) Replace "import org.apache.commons.lang."
> with "import org.apache.commons.lang3."
> I had about 170 occurrences.
> 3) Compile. If you have a compile error, look for that class on:
> https://commons.apache.org/proper/commons-lang/article3_0.html
> I only had 1 error. Replacing "StringEscapeUtils.escapeHtml(s)"
> with "StringEscapeUtils.ESCAPE_HTML4.translate(s)" fixed that.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7963) Require Maven 3.3.1+ and introduce mvnw
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/WFLY-7963?page=com.atlassian.jira.plugin.... ]
Peter Palaga updated WFLY-7963:
-------------------------------
Description:
* Maven 3.3.1+ is required by the Enforcer Plugin
* {{mvnw}} (a.k.a. Maven Wrapper) replaces the legacy {{tools/download-maven.*}} scripts
* {{build.*}} and {{integration-tests.*}} scripts were kept for backwards compatibility.
These changes were discussed on wildfly-dev mailing list.
was:
There are three closely related things here:
* Maven 3.3.1+ is required by the Enforcer Plugin
* mvnw (a.k.a. Maven Wrapper) is a script that downloads and installs
(if necessary) the required Maven version to ~/.m2/wrapper and runs it
from there. "mvn -N io.takari:maven:wrapper" was used to create all the
necessary files. The same command can be used in the future to upgrade
to a newer wrapper version. Maven version used by the wrapper is stored
in .mvn/wrapper/maven-wrapper.properties
* .mvn/jvm.config is a place where Maven 3.3.1+ looks for JVM parameters
(memory, etc.) which were traditionally defined in the MAVEN_OPTS
environment variable.
> Require Maven 3.3.1+ and introduce mvnw
> ---------------------------------------
>
> Key: WFLY-7963
> URL: https://issues.jboss.org/browse/WFLY-7963
> Project: WildFly
> Issue Type: Task
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> * Maven 3.3.1+ is required by the Enforcer Plugin
> * {{mvnw}} (a.k.a. Maven Wrapper) replaces the legacy {{tools/download-maven.*}} scripts
> * {{build.*}} and {{integration-tests.*}} scripts were kept for backwards compatibility.
> These changes were discussed on wildfly-dev mailing list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7963) Require Maven 3.3.1+ and introduce mvnw
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/WFLY-7963?page=com.atlassian.jira.plugin.... ]
Peter Palaga moved WFCORE-2232 to WFLY-7963:
--------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-7963 (was: WFCORE-2232)
Fix Version/s: (was: 3.0.0.Alpha18)
> Require Maven 3.3.1+ and introduce mvnw
> ---------------------------------------
>
> Key: WFLY-7963
> URL: https://issues.jboss.org/browse/WFLY-7963
> Project: WildFly
> Issue Type: Task
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> There are three closely related things here:
> * Maven 3.3.1+ is required by the Enforcer Plugin
> * mvnw (a.k.a. Maven Wrapper) is a script that downloads and installs
> (if necessary) the required Maven version to ~/.m2/wrapper and runs it
> from there. "mvn -N io.takari:maven:wrapper" was used to create all the
> necessary files. The same command can be used in the future to upgrade
> to a newer wrapper version. Maven version used by the wrapper is stored
> in .mvn/wrapper/maven-wrapper.properties
> * .mvn/jvm.config is a place where Maven 3.3.1+ looks for JVM parameters
> (memory, etc.) which were traditionally defined in the MAVEN_OPTS
> environment variable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2232) Require Maven 3.3.1+ and introduce mvnw
by Peter Palaga (JIRA)
Peter Palaga created WFCORE-2232:
------------------------------------
Summary: Require Maven 3.3.1+ and introduce mvnw
Key: WFCORE-2232
URL: https://issues.jboss.org/browse/WFCORE-2232
Project: WildFly Core
Issue Type: Task
Reporter: Peter Palaga
Assignee: Peter Palaga
Fix For: 3.0.0.Alpha18
There are three closely related things here:
* Maven 3.3.1+ is required by the Enforcer Plugin
* mvnw (a.k.a. Maven Wrapper) is a script that downloads and installs
(if necessary) the required Maven version to ~/.m2/wrapper and runs it
from there. "mvn -N io.takari:maven:wrapper" was used to create all the
necessary files. The same command can be used in the future to upgrade
to a newer wrapper version. Maven version used by the wrapper is stored
in .mvn/wrapper/maven-wrapper.properties
* .mvn/jvm.config is a place where Maven 3.3.1+ looks for JVM parameters
(memory, etc.) which were traditionally defined in the MAVEN_OPTS
environment variable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months