Jeff, how are you launching your app under eclipse? Are you making m2e fire
gwt:run, or are you using Google Plugin for Eclipse > Run as Web App?
On Thu, Sep 15, 2011 at 2:58 AM, Jeff Larsen <larse...@gmail.com> wrote:
> I know I would like it if the RequestFactory stuff was pushed into maven
> central.
>
> Don't make gwt-servlet into a real dependency, add it to the list of
> dependencies in your plugin.
>
>
> <plugin>
> <groupId>org.bsc.maven</**groupId>
> <artifactId>maven-processor-**plugin</artifactId>
> <version>2.0.5</version>
> <executions>
> <execution>
> <id>process</id>
> <goals>
> <goal>process</goal>
> </goals>
> <phase>generate-sources</**phase>
> <configuration>
> <!-- TODO(rjrjr) Can this explicit processor line go away if
>
> we depend
> on requestfactory-apt directly? Is that jar in maven
> central?
> -->
> <processors>
>
> <processor>com.google.web.**bindery.requestfactory.apt.**
> RfValidator</processor>
> </processors>
> </configuration>
> </execution>
> </executions>
> <dependencies>
> <dependency>
> <groupId>com.google.gwt</groupId>
> <artifactId>gwt-servlet</artifactId>
> <version>${gwt-version}</version>
> </dependency>
> </dependencies>
> </plugin>
> </plugins>
>
>
> When you switch that to requestfactory-apt, you should be able to get rid
> of the explicit binding as well, but I have it in mine for documentation
> purposes.
>
> I was just working on this last week for some annotation processors I've
> written for my application to get around writing the proxies for
> RequestFactory, building the columns that map to those proxies then also
> building the constantswithlookup to map the values in there.
>
> I needed to do some additional steps when doing this with m2e aswell. Since
> there are no m2e connectors for any of the annotation processor maven
> plugins, I worked around that with the build-helper plugin.
>
> The build helper plugin allows you to specify additional source folders, so
> I just mapped a new source folder to where my maven annotation processor was
> going. I think I found a bug in build-helper-connector where you can't
> specify source folders under target, but maybe you'll have better luck.
>
> Then because I added a new source folder, I needed to add the maven clean
> plugin to make sure the generated artifacts were getting removed every time
> a maven clean happened.
>
> tl;dr
>
> here are the relevant bits of the pom that I was using to get all this
> working together.
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>build-helper-maven-plugin</artifactId>
> <version>1.7</version>
> <executions>
> <execution>
> <id>add-source</id>
> <phase>generate-sources</phase>
> <goals>
> <goal>add-source</goal>
> </goals>
> <configuration>
> <sources>
> <source>${basedir}/generated-sources/annotations</source>
> </sources>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <artifactId>maven-clean-plugin</artifactId>
> <version>2.4.1</version>
> <configuration>
> <filesets>
> <fileset>
> <directory>generated-sources/annotations</directory>
> <includes>
> <include>**/*</include>
> </includes>
> </fileset>
> </filesets>
> </configuration>
> </plugin>
> <plugin>
>
> <groupId>org.bsc.maven</groupId>
> <artifactId>maven-processor-plugin</artifactId>
> <executions>
> <execution>
> <id>process</id>
> <goals>
> <goal>process</goal>
> </goals>
> <phase>generate-sources</phase>
> </execution>
> </executions>
> <dependencies>
> <dependency>
> <groupId>com.ecologic</groupId>
> <artifactId>rfprocessor</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> </dependency>
> </dependencies>
>
> <configuration>
> <outputDirectory>${basedir}/generated-sources/annotations</outputDirectory>
> <processors>
> <processor>com.ecologic.rfprocessor.CreateDefaults</processor>
> </processors>
> </configuration>
>
>
>
>
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
