Thanks - i'll give that a go tomorrow :-)
On Apr 16, 3:22 pm, eldzi <[email protected]> wrote:
> 1. build and install the plugin in the branch
> 2. put <artifactDevelProjects>projects.xml</artifactDevelProjects> in
> the configuration of the plugin
> 3. create and fill projects.xml file in the root of the ProjectGWT
> with something like this (change groupId, artifactId and path to pom):
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd";>
> <properties>
> <entry key="your.groupId:artifactId">/your/path/to/project/artifactId/
> pom.xml</entry>
> </properties>
>
> On 15. Apr, 13:50 h., Murray Waters <[email protected]> wrote:
>
> > Thanks - Once you have the patch, how do you use it?
>
> > Do you simply run "mvn com.totsp.gwt:maven-googlewebtoolkit2-
> > plugin:gwt" from the web project, and it works?
>
> > Cheers
>
> > On Apr 15, 5:09 pm, eldzi <[email protected]> wrote:
>
> > > yes that is possible but only if you build the plugin from branch
> > > "issue149".. some information is present in issue itself
> > > -http://code.google.com/p/gwt-maven/issues/detail?id=149
>
> > > you can directly bind directories with built classes instead of
> > > jars...
>
> > > On 15. Apr, 06:54 h., Murray Waters <[email protected]> wrote:
>
> > > > Just to be clear below, ProjectGWT is the only GWT project.
> > > > ProjectCommon is purely a jar project.
>
> > > > On Apr 15, 1:43 pm, Murray Waters <[email protected]> wrote:
>
> > > > > Hi,
>
> > > > > I've setup a multi module project, using the standard maven "flat"
> > > > > structure with a parent project.
>
> > > > > Ie
>
> > > > > ProjectParent - pom project
> > > > > ProjectCommon - jar project
> > > > > ProjectGWT - war project - depends on ProjectCommon.
>
> > > > > Typically (lets ignore GWT for a minute) this setup would allow
> > > > > project dependencies to work without needing to do a mvn:install. Ie
> > > > > my web project could depend on my common project, and doing a "mvn
> > > > > package" from the parent project would package the war with the
> > > > > depdendent jars including ProjectCommon.
>
> > > > > Using the m2eclipse plugin I get a similar result, ie when I modify
> > > > > something in ProjectCommon m2eclipse/wtp restarts the server and
> > > > > deploys the new code, without the requirement to do a "mvn install".
>
> > > > > Now what I want to do is to run the hosted mode browser and I can do
> > > > > this by running
> > > > > mvn com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt
> > > > > from the ProjectGWT folder, but only AFTER i have done a "mvn install"
> > > > > from the ProjectParent folder, otherwise it will attempt to download
> > > > > ProjectCommon from my local repository and fail.
>
> > > > > So is there a way to run the hosted mode browser without needing to
> > > > > perform an install of the dependent modules first?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"gwt-maven" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gwt-maven?hl=en
-~----------~----~----~----~------~----~------~--~---
