Great work Geoffrey. Thanks, Subhas
On Thu, Oct 14, 2010 at 12:24 PM, Michael Anstis <[email protected]>wrote: > Thanks for the clarification Geoffrey. > > > > On 14 October 2010 14:20, Geoffrey De Smet <[email protected]>wrote: > >> The eclipse GWT plugin doesn't use maven. >> >> >> With kind regards / Met vriendelijke groeten, >> Geoffrey De Smet >> >> Op 14-10-10 12:05, Anstis, Michael (M.) schreef: >> > Hi Geoffrey, Esteban, >> > The Eclipse GWT Plugin in essence calls out to GWT's >> > com.google.gwt.dev.DevMode and does not use maven. >> >> Yes, AFAIC it doesn't use maven. >> >> > I think half the problem could be the disjoint between the default paths >> > used by maven compared to the default paths used by gwt i.e. they are >> > different: mvn uses src/main/webapp by default whereas gwt prefers /war. >> >> The latest gwt plugin for eclipse (since 2.0.3) isn't hardcoded to the >> /war directory, so the /war issues is not longer relevant normally. >> See the note on >> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/war-folder.html >> So don't use an old gwt plugin for eclipse. >> Toni Rikkola is working fine with eclipse, maybe you can ask him how he >> said it up? >> >> > It looks like you can bring the two inline >> > http://mojo.codehaus.org/gwt-maven-plugin/user-guide/war-folder.htmlbut >> > I haven't tried it. A warning to this effect is in the log you show >> > "Your POM <build><outputdirectory> does not match your hosted webapp >> > WEB-INF/classes folder for GWT Hosted browser to see your classes." I >> > think the classes are JIT'ed so you won't get any errors until launching >> > your browser. I also think the "target" folder >> > ("/home/esteban/plugTree/trunkTMP/drools-guvnor/*target*/drools-guvnor") >> > is a GWT1.6 hang-over and wonder whether Guvnor is fully GWT2.x or a >> > hybrid of bits and pieces that wouldn't help matters. >> >> There is the sources wierdness. Basically gwt needs the *.java sources >> of all the java to javascript it needs to compile, not just the *.class >> sources. So to be able to compile drools-guvnor it needs the sources of >> drools-ide-common. >> - If you have drools open in IntelliJ/Eclipse, this isn't a problem: the >> sources are there anyway and you don't need to configure anything >> special. Note you can't have just drools-guvnor open without >> drools-ide-common open... I would expect this to be the same for netbeans >> - In Maven, things are different because modules need to be able to >> compile individually. There are 2 ways to handle it: >> -- the GWT hack way: just add the sources to the jar. This is the bad >> way as it violates the maven repository contract. >> -- the maven way (which we follow): also install/deploy the sources into >> the repository as a separate jar (so as a >> drools-idea-common-...-sources.jar) and re-use that to build >> drools-guvnor (and note that the maven intellij/eclipse reuse those >> sources to automatically download sources etc). >> >> > Not wanting to tread on toes. >> idem dito :) Hope this helps too >> >> > With kind regards, >> > Mike >> > >> > >> ------------------------------------------------------------------------ >> > *From:* [email protected] >> > [mailto:[email protected]] *On Behalf Of >> > *[email protected] >> > *Sent:* 14 October 2010 00:07 >> > *To:* Rules Dev List >> > *Subject:* Re: [rules-dev] Guvnor build changes summary >> > >> > Geoffrey, again, great work! >> > But I have a question for you. I'm trying to run/debug guvnor >> > without eclipse. >> > Thanks to your work, now I am able to execute *mvn gwt:compile* >> > without modify the pom.xml file! That is great. >> > Then I run Guvnor doing:* mvn -Dgwt.module=org.drools.guvnor.Guvnor >> > -DrunTarget=org.drools.guvnor.Guvnor/Guvnor.html gwt:debug* >> > Everything seams to look right. I get this output: >> > >> > /Preparing gwt:debug/ >> > /[resources:resources]/ >> > /Using 'UTF-8' encoding to copy filtered resources./ >> > /Copying 29 resources/ >> > /[compiler:compile]/ >> > /Nothing to compile - all classes are up to date/ >> > /[gwt:debug]/ >> > /starting debugger on port 8000 in suspend mode/ >> > /You're project declares dependency on gwt-user 2.0.4. This plugin >> > is designed for version 2.1-20101001.MGWT219/ >> > /create exploded Jetty webapp in >> > /home/esteban/plugTree/trunkTMP/drools-guvnor/target/drools-guvnor/ >> > /Your POM <build><outputdirectory> does not match your hosted webapp >> > WEB-INF/classes folder for GWT Hosted browser to see your classes./ >> > /Listening for transport dt_socket at address: 8000/ >> > >> > Now, when I try to attach a debugger (in my case, using Netbeans), I >> > get the following behavior: >> > >> > 1. The GWT Development Mode console appears >> > 2. After a few seconds, the Startup URL appears in the combobox >> > 3. At this point, I have some warnings in "Development Mode" and >> > "Jetty" tabs. (probably you are using tomcat, but should be >> > the same) >> > 4. When I try to enter Guvnor using firefox, a new tab appears in >> > the GWT Development Mode (which is the expected behavior), but >> > a lot of errors appear there. The errors are because the >> > source code of ide.common packages can't be found. >> > >> > >> > I'm attaching a screenshot showing the error: >> > >> > news:// >> news.gmane.org:119/C7774483B6A70C4BB10E917CC1A59DC10766BE79%40eu1wam35.warley.ford.com?group=gmane.comp.java.drools.devel&key=3996&header=quotebody&part=1.1.2&filename=Screenshot.png >> > >> > The questions are: do you know how is eclipse running guvnor? Does >> > it use maven at all? Am I missing any argument when running >> > gwt:debug goal? >> > >> > Best Regards, >> > >> > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >> > >> > Esteban Aliverti >> > - Developer @ http://www.plugtree.com <http://www.plugtree.com> >> > - Blog @ http://ilesteban.wordpress.com >> > >> > >> > On Sat, Oct 9, 2010 at 7:53 AM, Geoffrey De Smet >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > No, I no longer think we should "split up drools-guvnor into >> > drools-guvnor-gwtclient and drools-guvnor-server", >> > not at least until GWT supports separate client vs server >> > classpaths better. >> > I will still look into moving factconstraints module guvnor part >> to >> > guvnor (and the rest might be movable to drools-core/compiler?)? >> > >> > With kind regards, >> > Geoffrey De Smet >> > >> > Op 08-10-10 09:54, Anstis, Michael (M.) schreef: >> > > I'm not sure Geoffrey is planning on the split anymore: >> > >> I haven't split up drools-guvnor into >> > drools-guvnor-gwtclient and >> > >> drools-guvnor-server, because GWT simply doesn't really >> > allow that (not >> > >> without making the solution worse than the problem at >> least...). >> > > >> > > >> > >> ------------------------------------------------------------------------ >> > > *From:* [email protected] >> > <mailto:[email protected]> >> > > [mailto:[email protected] >> > <mailto:[email protected]>] *On Behalf Of >> > *Michael Neale >> > > *Sent:* 08 October 2010 03:34 >> > > *To:* Rules Dev List >> > > *Subject:* Re: [rules-dev] Guvnor build changes summary >> > > >> > > yes, that probably would make sense. Although, there would >> > have to >> > > be maybe a 3rd for the common code. Or else the server module >> > > depends on the client module? >> > > >> > > On Fri, Oct 8, 2010 at 12:51 PM, Jervis Liu <[email protected] >> > <mailto:[email protected]> >> > > <mailto:[email protected] <mailto:[email protected]>>> wrote: >> > > >> > > Good job, Geoffrey! BTW, what is this about: "split up >> > drools-guvnor >> > > into drools-guvnor-gwtclient and drools-guvnor-server" ? >> > > >> > > Thanks, >> > > Jervis >> > > >> > > Geoffrey De Smet wrote: >> > > > Hi guys, >> > > > >> > > > The Guvnor build has changed somewhat. Here's the changes: >> > > > - "mvn clean compile" now compiles the GWT java sources to >> > > javascript >> > > > with the gwt-maven-plugin. >> > > > -- So now, to really clean build guvnor, you don't need to >> > > run the ANT >> > > > script separate no more >> > > > -- The maven plugin is about 50% faster than the ANT >> script. >> > > > -- This makes the entire drools build slower (as it now gwt >> > > compiles >> > > > too), but I am looking into improving that (for example in >> a >> > > development >> > > > mode profile, we can only gwt compile to english and >> firefox) >> > > > - The generated GWT javascript files have been removed from >> > > subversion >> > > > and are now generated under the target/drools-guvnor >> directory >> > > > -- No more A43BF34D23567676DF.js files in svn or tree >> > > conflicts on those >> > > > directories >> > > > >> > > > I haven't split up drools-guvnor into >> > drools-guvnor-gwtclient and >> > > > drools-guvnor-server, because GWT simply doesn't really >> allow >> > > that (not >> > > > without making the solution worse than the problem at >> > least...). >> > > > >> > > > If you feel any rough edges, let me know and I 'll take a >> > > look at it. >> > > > >> > > > I 'll remove the old ANT script soon, once the maven >> > > filtering for the >> > > > version and revision is in place. >> > > > >> > > >> > > _______________________________________________ >> > > rules-dev mailing list >> > > [email protected] <mailto:[email protected]> >> > <mailto:[email protected] >> > <mailto:[email protected]>> >> > > https://lists.jboss.org/mailman/listinfo/rules-dev >> > > >> > > >> > > >> > > >> > > -- >> > > Michael D Neale >> > > home: www.michaelneale.net <http://www.michaelneale.net> >> > <http://www.michaelneale.net> >> > > blog: michaelneale.blogspot.com >> > <http://michaelneale.blogspot.com> >> > <http://michaelneale.blogspot.com> >> > > >> > > >> > > >> > > _______________________________________________ >> > > rules-dev mailing list >> > > [email protected] <mailto:[email protected]> >> > > https://lists.jboss.org/mailman/listinfo/rules-dev >> > >> > _______________________________________________ >> > rules-dev mailing list >> > [email protected] <mailto:[email protected]> >> > https://lists.jboss.org/mailman/listinfo/rules-dev >> > >> > >> > >> > >> > _______________________________________________ >> > rules-dev mailing list >> > [email protected] >> > https://lists.jboss.org/mailman/listinfo/rules-dev >> >> _______________________________________________ >> rules-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/rules-dev >> > > > _______________________________________________ > rules-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-dev > >
_______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
