Run GWT compiler from maven without any gwt-m-p restrictions. This can be useful for two main reasons: * Running the compiler during test (i.e. switch phase to process-test-classes, and set classpathScope to test) to allow the test phase to have compiled JS to work on * Running without skipping built-in entrypoints to completely verify that the …

gistfile1.txt

			<plugin>
				<groupId>org.codehaus.mojo</groupId>
				<artifactId>exec-maven-plugin</artifactId>
				<version>1.2.1</version>
				<executions>
					<execution>
						<id>compile-js</id>
						<phase>prepare-package</phase>
						<goals>
							<goal>exec</goal>
						</goals>
						<configuration>
							<executable>java</executable>
							<arguments>
								<argument>-classpath</argument>
								<classpath />
								<argument>com.google.gwt.dev.Compiler</argument>
								<argument>-war</argument>
								<argument>${project.build.directory}/www</argument>
								<argument>org.project.my.Module</argument>
							</arguments>
						</configuration>
					</execution>
				</executions>
			</plugin>