For future reference, is there a way to identify this kind of 'dependent' goal on a mojo wiki page?
Or alternatively, if there isn't a general way, could a note be put on this page: http://mojo.codehaus.org/gwt-maven-plugin/compile-mojo.html Thanks, Jacques On Fri, Mar 12, 2010 at 12:04 PM, nicolas de loof <[email protected]>wrote: > true > > > 2010/3/12 Jacques <[email protected]> > >> I can confirm that your solution works. >> >> So am I correct to understanding that gwt:compile shouldn't actually be >> called at the command line? >> >> >> On Fri, Mar 12, 2010 at 10:58 AM, nicolas de loof < >> [email protected]> wrote: >> >>> you don't have to "chain" gwt:generateAsync and then gwt:compile >>> source folder in maven are dynamically added >>> >>> just configure generateAsync as an execution so that is it automatically >>> executed during build (at generate-source phase by default) and run "mvn >>> install" >>> >>> >>> 2010/3/12 Jacques <[email protected]> >>> >>>> Posted project at http://whsaddins.com/gwtmin/gwtmin.zip >>>> >>>> unzip >>>> mvn gwt:generateAsync >>>> mvn gwt:compile >>>> >>>> Output: >>>> :::snip::: >>>> [ERROR] Line 26: SourceShimServiceAsync cannot be resolved to a type >>>> :::snip::: >>>> >>>> thanks, >>>> Jacques >>>> >>>> >>>> On Fri, Mar 12, 2010 at 10:02 AM, nicolas de loof < >>>> [email protected]> wrote: >>>> >>>>> Can't reproduce. >>>>> >>>>> IT test all generate async code and compile as expected >>>>> please post a test project demonstrating the issue >>>>> >>>>> 2010/3/12 Jacques <[email protected]> >>>>> >>>>> I'm using the latest 1.3 snapshot. When I attempt to compile a project >>>>>> where I've used mvn/gwt to generate the async interfaces to the default >>>>>> path >>>>>> target/generated_sources/gwt/, this path isn't included in the >>>>>> gwt:compile >>>>>> command. >>>>>> >>>>>> I confirmed that adding the path to the value provided in Build Error >>>>>> [INFO] Command [[{value}]] correctly compiles my project. I saw that >>>>>> this >>>>>> bug existed in *MGWT-26 <http://jira.codehaus.org/browse/MGWT-26> *but >>>>>> that seems to have been fixed in 1.1. I haven't tested other versions >>>>>> besides my current one. (Note that the generated classpath for gwt:run >>>>>> is >>>>>> fine.) >>>>>> >>>>>> Easy workarounds seem to be: >>>>>> >>>>>> 1. Move the async target directory to an existing included classpath >>>>>> folder (e.g. src/main/java) >>>>>> 2. Manually run GWT compile by simply taking the failed command >>>>>> execution and adding the required classpath. >>>>>> >>>>>> This issue was seen on Windows 7 using GWT 2.0.3, Maven 2.2.1, and >>>>>> gwt-maven-plugin version 1.3-20100212.080647-5 >>>>>> >>>>>> Let me know if I just made a foolish blunder. >>>>>> >>>>>> Thanks, >>>>>> Jacques >>>>>> >>>>>> :::::::::::::::::::pom.xml used ::::::::::::::::::::: >>>>>> >>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>> <project >>>>>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >>>>>> http://maven.apache.org/xsd/maven-4.0.0.xsd"; >>>>>> xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" >>>>>> http://www.w3.org/2001/XMLSchema-instance";> >>>>>> <modelVersion>4.0.0</modelVersion> >>>>>> >>>>>> <groupId>com.example</groupId> >>>>>> <artifactId>example</artifactId> >>>>>> <version>1.0-SNAPSHOT</version> >>>>>> <packaging>war</packaging> >>>>>> >>>>>> <build> >>>>>> <plugins> >>>>>> <plugin> >>>>>> <groupId>org.codehaus.mojo</groupId> >>>>>> <artifactId>gwt-maven-plugin</artifactId> >>>>>> <version>1.3-SNAPSHOT</version> >>>>>> <executions> >>>>>> <execution> >>>>>> <goals> >>>>>> <goal>compile</goal> >>>>>> <goal>generateAsync</goal> >>>>>> <goal>test</goal> >>>>>> </goals> >>>>>> </execution> >>>>>> </executions> >>>>>> <configuration> >>>>>> <runTarget>Example.html</runTarget> >>>>>> <hostedWebapp> >>>>>> ${project.build.directory}/${project.build.finalName} >>>>>> </hostedWebapp> >>>>>> </configuration> >>>>>> </plugin> >>>>>> >>>>>> </plugins> >>>>>> </build> >>>>>> <dependencies> >>>>>> <dependency> >>>>>> <groupId>com.google.gwt</groupId> >>>>>> <artifactId>gwt-servlet</artifactId> >>>>>> <version>${gwt.version}</version> >>>>>> <scope>runtime</scope> >>>>>> </dependency> >>>>>> <dependency> >>>>>> <groupId>com.google.gwt</groupId> >>>>>> <artifactId>gwt-user</artifactId> >>>>>> <version>${gwt.version}</version> >>>>>> <scope>provided</scope> >>>>>> </dependency> >>>>>> <dependency> >>>>>> <groupId>com.google.code.gwt-log</groupId> >>>>>> <artifactId>gwt-log</artifactId> >>>>>> <version>3.0.0</version> >>>>>> </dependency> >>>>>> >>>>>> <dependency> >>>>>> <groupId>junit</groupId> >>>>>> <artifactId>junit</artifactId> >>>>>> <version>4.4</version> >>>>>> <scope>test</scope> >>>>>> </dependency> >>>>>> </dependencies> >>>>>> <properties> >>>>>> <gwt.version>2.0.3</gwt.version> >>>>>> <maven.compiler.source>1.6</maven.compiler.source> >>>>>> <maven.compiler.target>1.6</maven.compiler.target> >>>>>> </properties> >>>>>> </project> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >
