Re: RE : RE : [rules-users] Do you have a Bug?

Hello, I Had the same probleme with maven 2.0.8 (I used this before) and in the documentation, it is written that maven 2.0.6 is needed, so I went back to 2.0.6 but no change Nicolas (my first name)

-------- Message d'origine-------- De: rules-users-bounces(a)lists.jboss.org de la part de Edson Tirelli Date: jeu. 13/03/2008 14:34 À: Rules Users List Objet : Re: RE : [rules-users] Do you have a Bug? Héron, We are looking into the plugin build error. Meanwhile, please update to maven 2.0.8. Unfortunately maven is having some problems to build with different versions. []s Edson 2008/3/13, Héron Nicolas <nheron(a)sopragroup.com&gt;: > > Hello, > I am trying to compile the 4.0.x and > 1) there are always test unit not working => I have to skip the test in > maven > 2) > get the following error > > [java] /home/nheron/workspace-source-drools-4.0.x/jbossrules/drools- > eclipse3.2/target/eclipse/plugins/org.eclipse.pde.build_3.2.1.r321_v20060823/scripts/genericTargets.xml:80: > Unable to find plug-in: org.drools.eclipse_0.0.0. Please check the error > log for more details. > > [java] Total time: 2 seconds > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Error executing ant tasks > > Embedded error: Java returned: 13 > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error executing > ant tasks > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > DefaultLifecycleExecutor.java:564) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle > (DefaultLifecycleExecutor.java:480) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > (DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > (DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( > DefaultLifecycleExecutor.java:278) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( > DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java > :315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode( > Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing > ant tasks > at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks( > AbstractAntMojo.java:114) > at org.apache.maven.plugin.antrun.AntRunMojo.execute( > AntRunMojo.java:83) > at org.apache.maven.plugin.DefaultPluginManager.executeMojo( > DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: Java returned: 13 > at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java > :275) > at org.apache.tools.ant.Task.perform(Task.java:364) > at org.apache.tools.ant.Target.execute(Target.java:341) > at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks( > AbstractAntMojo.java:108) > ... 19 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 1 minute 29 seconds > [INFO] Finished at: Thu Mar 13 13:47:49 CET 2008 > [INFO] Final Memory: 23M/44M > [INFO] > ------------------------------------------------------------------------ > > > What did i do wrong ? > I use maven 2.0.6, ant 1.7.0 , jdk 1.5 b13 > > > I had problems with dynamic rules in drools 4.0.4 which I don't have any > more in a drools 5 snapshot through the hudson stuf. > > Thanks > regards > Nicolas Héron > > -------- Message d'origine-------- > De: rules-users-bounces(a)lists.jboss.org de la part de Mark Proctor > Date: jeu. 13/03/2008 03:17 > À: Rules Users List; Rules Dev List > Objet : [rules-users] Do you have a Bug? > > We've fixed a huge number of things for 4.0.5. We are going to try and > get the release out this friday. So please hurry if you have a bug then > let us know, especially if you have a fix :) And don't forget to try > your bug out on 4.0.x in svn in case its already fixed: > > http://anonsvn.labs.jboss.com/labs/jbossrules/branches/4.0.x/ > > Mark > > Mark Proctor wrote: > > Narendra Valada wrote: > >> I had reported an issue a couple of weeks ago with nested inner > >> classes not being handled correctly. > >> > >> I made some changes to the org.drools.base.ClassTypeResolver class to > >> resolve it and everything appears to work fine. > >> > >> How do I provide the fix and test case to you? Do you want me to > >> raise a JIRA? > > Yes you will need to raise a JIRA. At this stage we have no plans to > > fix this, as we can consider inner inner classes esoteric enough to > > say it's unsupported. Although if someone can provide a clean patch, > > it would be nice to fix. You'll have to be quick though, if you want > > the fix in 4.0.5 > >> > >> Thanks, > >> > >> Narendra > >> > >> > >> On 3/8/08, *Mark Proctor* <mproctor(a)codehaus.org > >> <mailto:mproctor@codehaus.org <mailto:mproctor@codehaus.org%20%3Cmproctor@codehaus.org>>>> wrote: > >> > >> We are about to release 4.0.5, next week. This has a large number > >> of bug > >> fixes, especially multi-threading bugs. Anyone that has production > >> issues can you please do a checkout for the 4.0.x branch asap and > >> provide us with a test case if it is not fixed. If you don't get > your > >> test case to us by end of monday, start of tuesday, you'll have > >> to wait > >> another 2 months+ for 4.0.6. > >> http://anonsvn.labs.jboss.com/labs/jbossrules/branches/4.0.x/ > >> > >> Mark > >> _______________________________________________ > >> rules-users mailing list > >> rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org <mailto:rules-users@lists.jboss.org%3Crules-users@lists.jboss.org>> > > > >> https://lists.jboss.org/mailman/listinfo/rules-users > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> rules-users mailing list > >> rules-users(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/rules-users > >> > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > rules-users mailing list > > rules-users(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/rules-users > > > > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > > -- Edson Tirelli JBoss Drools Core Development Office: +55 11 3529-6000 Mobile: +55 11 9287-5646 JBoss, a division of Red Hat @ www.jboss.com ------------------------------------------------------------------------ _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users