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 <jliu@redhat.com> 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
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev



--
Michael D Neale
home: www.michaelneale.net
blog: michaelneale.blogspot.com