April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3403) drools-camel-server-5.3.x.Final.war - strict web application container complains about web.xml

by Nicholas DiPiazza (JIRA)

Nicholas DiPiazza created JBRULES-3403: ------------------------------------------ Summary: drools-camel-server-5.3.x.Final.war - strict web application container complains about web.xml Key: JBRULES-3403 URL: https://issues.jboss.org/browse/JBRULES-3403 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-camel Affects Versions: 5.3.1.Final, 5.3.0.Final Environment: Problem reproduces in WebLogic 10.x, maybe more? Reporter: Nicholas DiPiazza Assignee: Mark Proctor Priority: Minor Seems like "strict" J2EE containers require the <servlet>'s <display-name> to come before <servlet-name>, in particular WebLogic requires this. If this: <servlet> <servlet-name>CXFServlet</servlet-name> <display-name>CXF Servlet</display-name> <servlet-class> org.apache.cxf.transport.servlet.CXFServlet </servlet-class> <load-on-startup>1</load-on-startup> </servlet> were changed to this: <servlet> <display-name>CXF Servlet</display-name> <servlet-name>CXFServlet</servlet-name> <servlet-class> org.apache.cxf.transport.servlet.CXFServlet </servlet-class> <load-on-startup>1</load-on-startup> </servlet> the 5.3.0.Final and 5.3.1.Final drools-camel war files would be one step towards deploying with no changes out-of-the-box on WebLogic 10.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3268) Support for varargs needed

by Martin A (Created) (JIRA)

Support for varargs needed -------------------------- Key: JBRULES-3268 URL: https://issues.jboss.org/browse/JBRULES-3268 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Final Reporter: Martin A Assignee: Mark Proctor Priority: Minor I have a method such as: /* * determines if any of the events passed as parameter has occurred */ public boolean hasAnyEventOccurred(String... events) { for (String s : events) { if (hasEventOccurred(s)) { return true; } } return false; } However in rules I can't call it like that: hasAnyEventOccurred("event1", "event2", "event3"), I have to workaround as so: hasAnyEventOccurred(new String[] {"event1", "event2", "event3"}) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2805) Problem getting and using drools-api SNAPSHOT version from jboss maven repo

by Kris Verlaenen (JIRA)

Problem getting and using drools-api SNAPSHOT version from jboss maven repo --------------------------------------------------------------------------- Key: JBRULES-2805 URL: https://jira.jboss.org/browse/JBRULES-2805 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assignee: Geoffrey De Smet When adding drools-api as a dependency of another maven project, it will try to download the drools-api jar from the jboss maven repo, but then fail to download its parent somehow. If you first build drools locally, it can then find the parent pom in the repository succesfully. [INFO] snapshot org.drools:drools-api:5.2.0.SNAPSHOT: checking for updates from jboss-public-repository-group Downloading: https://repository.jboss.org/nexus/content/groups/public//org/drools/droo... 6K downloaded (drools-api-5.2.0.20101123.060233-380.pom) [INFO] snapshot org.drools:drools:5.2.0.SNAPSHOT: checking for updates from jboss-public-repository-group Downloading: https://repository.jboss.org/nexus/content/groups/public//org/drools/droo... [INFO] Unable to find resource 'org.drools:drools:pom:5.2.0.SNAPSHOT' in repository jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: null:drools-api:jar:null Reason: Cannot find parent: org.drools:drools for project: null:drools-api:jar:null for project null:drools-api:jar:null -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1801) drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref

by Juergen none (JIRA)

drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1801 URL: https://jira.jboss.org/jira/browse/JBRULES-1801 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 4.0.7 Reporter: Juergen none Assignee: Mark Proctor drools-4.0.7: Original error in build.xml: /home/juergen/workspace/eclipse/kusss-dev/build.xml:777: RuleBaseTask failed: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java' Traceback to: org.drools.compiler.PackageBuilderConfiguration, line 154+: Class cls = classLoader.loadClass( dialectClass ); DialectConfiguration dialectConf = (DialectConfiguration) cls.newInstance(); cls is org.drools.rule.builder.dialect.java.JavaDialectConfiguration, but loaded via classloader given in drools compile ant task property classpathref, while DialectConfiguration is loaded via ant tool classpath used for taskdef --> java.lang.ClassCastException: org.drools.rule.builder.dialect.java.JavaDialectConfiguration interim fix: make sure drools-compiler.jar is not in classpath of classloaderref suggested fix: Class cls = DialectConfiguration.class.getClassLoader().loadClass( dialectClass ); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1273) Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)

by Rainer Langbehn (JIRA)

Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task) ---------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1273 URL: http://jira.jboss.com/jira/browse/JBRULES-1273 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Rainer Langbehn Assigned To: Mark Proctor I already created the requested maven2 plugin and i would like to contribute it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
26
0 / 0

[JBoss JIRA] (AS7-4214) Operation rolled back using rollback-across-groups rollout plan returns success

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-4214: ------------------------------------- Summary: Operation rolled back using rollback-across-groups rollout plan returns success Key: AS7-4214 URL: https://issues.jboss.org/browse/AS7-4214 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final Reporter: Dominik Pospisil Assignee: Brian Stansberry If there are multiple server groups involved in management operation and one group fails and the rollback of the other groups is forced by using rollback-across-groups rollout plan the operation still return success. I think that in such situation the operation should return failure as the operation is not executed on any of the servers. Example of the outcome of a operation which failed on main-one and main-three and was rolled back on main-two and test-one: [CLI-out] { [CLI-out] "outcome" => "success", [CLI-out] "result" => undefined, [CLI-out] "server-groups" => { [CLI-out] "main-server-group" => { [CLI-out] "main-one" => { [CLI-out] "host" => "master", [CLI-out] "response" => { [CLI-out] "outcome" => "failed", [CLI-out] "failure-description" => {"JBAS014671: Failed services" => {"jboss.web.connector.test-http" => "org.jboss.msc.service.StartException in service jboss.web.connector.test-http: JBAS018007: Error starting web connector"}}, [CLI-out] "rolled-back" => true, [CLI-out] "response-headers" => {"process-state" => "restart-required"} [CLI-out] } [CLI-out] }, [CLI-out] "main-two" => { [CLI-out] "host" => "master", [CLI-out] "response" => { [CLI-out] "outcome" => "failed", [CLI-out] "rolled-back" => true [CLI-out] } [CLI-out] }, [CLI-out] "main-three" => { [CLI-out] "host" => "slave", [CLI-out] "response" => { [CLI-out] "outcome" => "failed", [CLI-out] "result" => undefined, [CLI-out] "failure-description" => {"JBAS014671: Failed services" => {"jboss.web.connector.test-http" => "org.jboss.msc.service.StartException in service jboss.web.connector.test-http: JBAS018007: Error starting web connector"}}, [CLI-out] "rolled-back" => true [CLI-out] } [CLI-out] } [CLI-out] }, [CLI-out] "test-server-group" => {"test-one" => { [CLI-out] "host" => "master", [CLI-out] "response" => { [CLI-out] "outcome" => "failed", [CLI-out] "rolled-back" => true [CLI-out] } [CLI-out] }} [CLI-out] } [CLI-out] } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2384) Unable to process deployment descriptor for context'/drools-server'

by Megha Shetty (JIRA)

Unable to process deployment descriptor for context'/drools-server' ------------------------------------------------------------------- Key: JBRULES-2384 URL: https://jira.jboss.org/jira/browse/JBRULES-2384 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Environment: windows Reporter: Megha Shetty Assignee: Mark Proctor I am getting the following error when i am trying to deploy drools-server.war through jboss. Unable to process deployment descriptor for context'/drools-server' Following is the complete log when i am starting the jboss server JAVA_HOME is not set. Unexpected results may occur. Set JAVA_HOME to the directory of your local JDK to avoid this message. =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: E:\Eclipse Europa\jboss-4.2.3.GA JAVA: java JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcIn terval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: E:\Eclipse Europa\jboss-4.2.3.GA\bin\run.jar =============================================================================== 14:35:43,295 INFO [Server] Starting JBoss (MX MicroKernel)... 14:35:43,295 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag= JBoss_4_2_3_GA date=200807181417) 14:35:43,295 INFO [Server] Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA 14:35:43,295 INFO [Server] Home URL: file:/E:/Eclipse Europa/jboss-4.2.3.GA/ 14:35:43,295 INFO [Server] Patch URL: null 14:35:43,295 INFO [Server] Server Name: default 14:35:43,295 INFO [Server] Server Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se rver\default 14:35:43,311 INFO [Server] Server Home URL: file:/E:/Eclipse Europa/jboss-4.2.3 .GA/server/default/ 14:35:43,311 INFO [Server] Server Log Dir: E:\Eclipse Europa\jboss-4.2.3.GA\ser ver\default\log 14:35:43,311 INFO [Server] Server Temp Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se rver\default\tmp 14:35:43,311 INFO [Server] Root Deployment Filename: jboss-service.xml 14:35:43,482 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 14:35:43,482 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,S un Microsystems Inc. 14:35:43,498 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:35:43,857 INFO [Server] Core system initialized 14:35:45,670 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 / 14:35:45,670 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml 14:35:46,513 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 14:35:46,513 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 14:35:46,701 INFO [TransactionManagerService] Starting recovery manager 14:35:46,748 INFO [TransactionManagerService] Recovery manager started 14:35:46,748 INFO [TransactionManagerService] Binding TransactionManager JNDI R eference 14:35:50,263 INFO [EJB3Deployer] Starting java:comp multiplexer 14:35:51,607 INFO [NativeServerConfig] JBoss Web Services - Native 14:35:51,622 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200 803312044) 14:35:52,466 INFO [Embedded] Catalina naming disabled 14:35:52,575 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java .library.path: C:\WINDOWS\system32;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32 ;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem 14:35:52,607 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0 .1-8080 14:35:52,607 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80 09 14:35:52,607 INFO [Catalina] Initialization processed in 147 ms 14:35:52,607 INFO [StandardService] Starting service jboss.web 14:35:52,607 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA 14:35:52,638 INFO [Catalina] Server startup in 24 ms 14:35:52,794 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w eb.deployer/ROOT.war/ 14:35:53,560 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/ http-invoker.sar/invoker.war/ 14:35:53,669 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/ jbossws.sar/jbossws-context.war/ 14:35:53,732 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../ deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 14:35:54,153 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep loy/management/console-mgr.sar/web-console.war/ 14:35:54,513 INFO [MailService] Mail Service bound to java:/Mail 14:35:54,669 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-local-jdbc.rar 14:35:54,763 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-xa-jdbc.rar 14:35:54,856 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-local-jdbc.rar 14:35:54,935 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-xa-jdbc.rar 14:35:55,544 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jms/jms-ra.rar 14:35:55,716 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/mail-ra.rar 14:35:55,903 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/quartz-ra.rar 14:35:55,903 INFO [QuartzResourceAdapter] start quartz!!! 14:35:55,950 INFO [SimpleThreadPool] Job execution threads will use class loade r of thread: main 14:35:55,950 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 14:35:55,966 INFO [RAMJobStore] RAMJobStore initialized. 14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule r' initialized from default resource file in Quartz package: 'quartz.properties' 14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 14:35:55,966 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS TERED started. 14:35:56,966 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 14:35:57,200 INFO [A] Bound to JNDI name: queue/A 14:35:57,200 INFO [B] Bound to JNDI name: queue/B 14:35:57,200 INFO [C] Bound to JNDI name: queue/C 14:35:57,200 INFO [D] Bound to JNDI name: queue/D 14:35:57,200 INFO [ex] Bound to JNDI name: queue/ex 14:35:57,216 INFO [testTopic] Bound to JNDI name: topic/testTopic 14:35:57,216 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 14:35:57,216 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 14:35:57,216 INFO [testQueue] Bound to JNDI name: queue/testQueue 14:35:57,231 INFO [UILServerILService] JBossMQ UIL service available at : /127. 0.0.1:8093 14:35:57,263 INFO [DLQ] Bound to JNDI name: queue/DLQ 14:35:57,341 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 14:35:57,794 INFO [TomcatDeployer] deploy, ctxPath=/drools-guvnor, warUrl=.../d eploy/drools-guvnor.war/ 14:36:08,965 INFO [TomcatDeployer] deploy, ctxPath=/drools-server, warUrl=.../d eploy/drools-server.war/ 14:36:09,012 WARN [config] Unable to process deployment descriptor for context '/drools-server' 14:36:09,371 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep loy/jmx-console.war/ 14:36:09,496 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8 080 14:36:09,512 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 14:36:09,512 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos s_4_2_3_GA date=200807181417)] Started in 26s:201ms -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-4360) hoernetq acceptor params need to subresources

by Heiko Braun (JIRA)

Heiko Braun created AS7-4360: -------------------------------- Summary: hoernetq acceptor params need to subresources Key: AS7-4360 URL: https://issues.jboss.org/browse/AS7-4360 Project: Application Server 7 Issue Type: Feature Request Components: JMS Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.2.Final i.e. to allow /subsystem=messaging/hornetq-server=default/acceptor=test/param=test:add(value=foobar) currently I cannot add any parameter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JBRULES-3276) Make Drools javadoc available online

by Richard Calmbach (Created) (JIRA)

Make Drools javadoc available online ------------------------------------ Key: JBRULES-3276 URL: https://issues.jboss.org/browse/JBRULES-3276 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.3.0.Final, 5.2.0.Final Reporter: Richard Calmbach Assignee: Mark Proctor The javadoc for Drools has not been available online since v5.1.1. If it is somewhere, it is not linked up from the obvious place at http://www.jboss.org/drools/documentation. Tasks: 1. Make Drools javadoc available online (not just as a download) concurrently with releases. 2. Link to javadoc from http://www.jboss.org/drools/documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3335) mvn eclipse:eclipse broken for drools-persistence-jpa

by Adar Dembo (Created) (JIRA)

mvn eclipse:eclipse broken for drools-persistence-jpa ----------------------------------------------------- Key: JBRULES-3335 URL: https://issues.jboss.org/browse/JBRULES-3335 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.1.Final Reporter: Adar Dembo Assignee: Mark Proctor >From a clean repository, I'm seeing a maven error when I run "mvn eclipse:eclipse": {noformat} [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Drools multiproject [INFO] Drools :: Core [INFO] Drools :: Compiler [INFO] Drools :: Templates [INFO] Drools :: Decision Tables [INFO] Drools :: JSR-94 API Module [INFO] Drools :: Clips [INFO] Drools :: Verifier [INFO] Drools :: Persistence :: JPA [INFO] Drools examples [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools multiproject 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-multiproject >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-multiproject --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-multiproject <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-multiproject --- [INFO] Not running eclipse plugin goal for pom project [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Core 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-core >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-core --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-core <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-core --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-core/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-core" to /home/adar/Source/drools/drools-core. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Compiler 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-compiler >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-compiler --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-compiler <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-compiler --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-compiler/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-compiler" to /home/adar/Source/drools/drools-compiler. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Templates 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-templates >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-templates --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-templates <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-templates --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-templates/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-templates" to /home/adar/Source/drools/drools-templates. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Decision Tables 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-decisiontables >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-decisiontables --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-decisiontables <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-decisiontables --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-decisiontables/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-decisiontables" to /home/adar/Source/drools/drools-decisiontables. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: JSR-94 API Module 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-jsr94 >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-jsr94 --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-jsr94 <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-jsr94 --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-jsr94/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-jsr94" to /home/adar/Source/drools/drools-jsr94. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Clips 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-clips >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-clips --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-clips <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-clips --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-clips/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-clips" to /home/adar/Source/drools/drools-clips. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Verifier 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-verifier >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-verifier --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-verifier <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-verifier --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /home/adar/Source/drools/drools-verifier/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "drools-verifier" to /home/adar/Source/drools/drools-verifier. [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Persistence :: JPA 5.4.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-persistence-jpa >>> [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-persistence-jpa --- [INFO] [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-persistence-jpa <<< [INFO] [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-persistence-jpa --- [INFO] Using Eclipse Workspace: null [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Resource directory's path matches an existing source directory. Resources will be merged with the source directory src/test/resources [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Drools multiproject ............................... SUCCESS [0.873s] [INFO] Drools :: Core .................................... SUCCESS [1.087s] [INFO] Drools :: Compiler ................................ SUCCESS [0.758s] [INFO] Drools :: Templates ............................... SUCCESS [0.374s] [INFO] Drools :: Decision Tables ......................... SUCCESS [0.341s] [INFO] Drools :: JSR-94 API Module ....................... SUCCESS [0.219s] [INFO] Drools :: Clips ................................... SUCCESS [0.073s] [INFO] Drools :: Verifier ................................ SUCCESS [0.102s] [INFO] Drools :: Persistence :: JPA ...................... FAILURE [0.225s] [INFO] Drools examples ................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 8.294s [INFO] Finished at: Thu Jan 05 15:30:50 PST 2012 [INFO] Final Memory: 27M/618M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on project drools-persistence-jpa: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[], exclude=[**/*.h2.db|**/*.java], test=true, filtering=true, merging with=resource src/test/resources: output=target/test-classes, include=[**/*.h2.db], exclude=[**/*.java], test=true, filtering=false -> [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 [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :drools-persistence-jpa {noformat} Here's my maven version: {noformat} Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) Maven home: /home/adar/Source/apache-maven-3.0.3 Java version: 1.6.0_26, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.0.0-14-generic", arch: "amd64", family: "unix" {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012