Re: [rules-dev] Guvnor build problems? -> Tomcat

I don't know who broke it, but I 'll see if I can get it fixed Op 20-01-11 09:20, Michael Anstis schreef: > Hi Ge0ffrey, > >> Does it occur in hosted mode in Eclipse/IntelliJ? >> Looks like the test classes are also copied into the war?!? >> Tihomir might know more about the whole role based stuff. > - It occurs when deploying to Tomcat (any Servlet Container?). > - The WAR *does* contain all "test" classes\resources. > - It does not occur in hosted mode (as I can remove "test" > classes\resources from the classpath). > - Seam is correct in reporting the error (as two classes are declared > as being the same component, because of the inclusion of "test" classes). > > So I'd surmise a compile problem with maven (but it could be old news)? > > With kind regards, > > Mike > > On 20 January 2011 07:56, Geoffrey De Smet&lt;ge0ffrey.spam(a)gmail.com > <mailto:ge0ffrey.spam@gmail.com>> wrote: > > > > Op 19-01-11 22:33, Michael Anstis schreef: > > Hi, > > > > I tried building a WAR for Guvnor and found a couple of hick-ups > > (although it was with my local copy of master taken a few months > ago). > > > > I mention them here in case they are unknown issues (feel free > to beat > > me up if I simply need to resync with master; which will happen as > > part of my dtable commit...) > > > > 1) In \drools-guvnor > > > > mvn package -DskipTests=true -PfullProfile > > > > Didn't build dependant drools-ide-common, as I'd expect and I had to > > "mvn install" this first. > This is partially normal... > mvn install = mvn package (=make the jar) + copy the jar in the local > repository > mvn package = mvn compile + ... + make the jar > > But for normal java apps, mvn compile is enough even in a > multi-module, > because it doesn't need to create a jar (or copy that in the local > repo) > as it justs reuses drools-ide-common/target/classes in the > classpath of > drools-guvnor. > Just like your Eclipse/IntelliJ does (because if were to build a jar > each time it would take as long as the maven build). > However, that might not work for GWT compilation, > so the safest bet it to do mvn install... > > > > 2) In \drools-guvnor > > > > mvn package -DskipTests=true -PfullProfile > > > > Built the WAR however the test classes are also included, > leading to a > > Seam error when deploying:- > > > > SEVERE: Exception sending context initialized event to listener > > instance of class org.jboss.seam.servlet.SeamListener > > java.lang.IllegalStateException: Two components with the same > name and > > precedence - component name: > > org.drools.guvnor.server.security.RoleBasedPermissionStore, > component > > classes: > > org.drools.guvnor.server.security.MockRoleBasedPermissionStore, > > org.drools.guvnor.server.security.RoleBasedPermissionStore > > at > > > org.jboss.seam.init.Initialization.addComponentDescriptor(Initialization.java:586) > > at > > > org.jboss.seam.init.Initialization.installScannedComponentAndRoles(Initialization.java:927) > > at > > > org.jboss.seam.init.Initialization.scanForComponents(Initialization.java:874) > > at > org.jboss.seam.init.Initialization.init(Initialization.java:687) > > > > This traced back to "MockRoleBasedPermissionStore" in the test > classes > > and "RoleBasedPermissionStore" in the non-test classes. > > > > Tomcat 6.x. > > Does it occur in hosted mode in Eclipse/IntelliJ? > Looks like the test classes are also copied into the war?!? > Tihomir might know more about the whole role based stuff. > > > > 3) Alot of Guvnor tests failed, however I assume Toni Rikkola could > > have fixed recently with his work in this area. > > If they talk about a repository lock failing, it's cool and Toni's > working on it. > If it's something else, it's not cool. > > > > Cheers, > > > > Mike > > > > > > _______________________________________________ > > rules-dev mailing list > > rules-dev@lists.jboss.org<mailto:rules-dev@lists.jboss.org> > > https://lists.jboss.org/mailman/listinfo/rules-dev > > -- > With kind regards, > Geoffrey De Smet > > > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org<mailto:rules-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/rules-dev > > > > _______________________________________________ > rules-dev mailing list > rules-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev