Hide Forgot
Date of First Response: 2010-02-08 11:20:59 securitylevel_name: Public The error log looks like: INFO] [compiler:compile] DEBUG util.py:256: [INFO] Compiling 337 source files to /maven/build/labs/jbossrules/soa_branches/BRMS-5.0.1/drools-compiler/target/classes DEBUG util.py:256: [INFO] ------------------------------------------------------------------------ DEBUG util.py:256: [ERROR] BUILD FAILURE DEBUG util.py:256: [INFO] ------------------------------------------------------------------------ DEBUG util.py:256: [INFO] Compilation failure DEBUG util.py:256: /maven/build/labs/jbossrules/soa_branches/BRMS-5.0.1/drools-compiler/src/main/java/org/drools/guvnor/server/util/GuidedDTDRLPersistence.java:[209,28] name clash: find(java.util.List<org.drools.guvnor.client.modeldriven.brl.FactPattern>,java.lang.String) and find(java.util.List<org.drools.guvnor.server.util.GuidedDTDRLPersistence.LabelledAction>,java.lang.String) have the same erasure DEBUG util.py:256: /maven/build/labs/jbossrules/soa_branches/BRMS-5.0.1/drools-compiler/src/main/java/org/drools/guvnor/server/util/GuidedDTDRLPersistence.java:[159,49] find(java.util.List<org.drools.guvnor.server.util.GuidedDTDRLPersistence.LabelledAction>,java.lang.String) in org.drools.guvnor.server.util.GuidedDTDRLPersistence cannot be applied to (java.util.List<org.drools.guvnor.client.modeldriven.brl.FactPattern>,java.lang.String) DEBUG util.py:256: [INFO] ------------------------------------------------------------------------ DEBUG util.py:256: [INFO] For more information, run Maven with the -e switch DEBUG util.py:256: [INFO] ------------------------------------------------------------------------ DEBUG util.py:256: [INFO] Total time: 1 minute 41 seconds DEBUG util.py:256: [INFO] Finished at: Fri Jan 29 13:28:06 GMT-05:00 2010 DEBUG util.py:256: [INFO] Final Memory: 21M/124M
Two private functions name has same name and similar parameter and will be blocked by JDK 1.5.0_18 compiler. The solution is to change the two function name to avoid the name clash. Fixed at https://svn.jboss.org/repos/labs/labs/jbossrules/soa_branches/BRMS-5.0.1 It had been fixed already in drools-trunk code base.
I'm assuming that this was a build issue, not something that clients would have encountered