Javascript not updated after full rebuild

56 views
Skip to first unread message

Nicolas J.

unread,
Oct 10, 2012, 12:35:07 PM10/10/12
to codehaus-mojo-gwt-...@googlegroups.com
Hello,

we are using the GWT maven plugin 2.4.0 on Linux in the command line, and we've noticed that after "mvn clean" + "mvn install", the Javascript isn't updated correctly. The build fully regenerates .js files correctly on the eclipse m2e plugin.

Any clue how to correct or bypass this issue ? This is a critical issue for us as the Linux build is the production one.

Our main pom.xml contains this:


    <build>
        <finalName>XXXApp</finalName>
        <outputDirectory>${webappDirectory}/WEB-INF/classes</outputDirectory>
        <plugins>
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>gwt-maven-plugin</artifactId>
                <version>${gwtVersion}</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>compile</goal>
                            <!-- <goal>resources</goal> -->
                            <!--<goal>generateAsync</goal> <goal>test</goal> -->
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <runTarget>XXXApp15.html</runTarget>
                    <hostedWebapp>${webappDirectory}</hostedWebapp>
 
                    <!-- for production use replace style PRETTY by OBF -->
                    <style>PRETTY</style>
                </configuration>
            </plugin>
            <!-- Copy static web files before executing gwt:run -->
<!--             <plugin> -->
<!--             <groupId>org.apache.maven.plugins</groupId> -->
<!--             <artifactId>maven-war-plugin</artifactId> -->
<!--             <version>2.1.1</version> -->
<!--             <executions> -->
<!--             <execution> -->
<!--             <phase>compile</phase> -->
<!--             <goals> -->
<!--             <goal>exploded</goal> -->
<!--             </goals> -->
<!--             </execution> -->
<!--             </executions> -->
<!--             <configuration> -->
<!--             <webappDirectory>${webappDirectory}</webappDirectory> -->
<!--             </configuration> -->
<!--             </plugin> -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>2.3.2</version>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
        </plugins>
    </build>

Best regards,

Nicolas

Rob Ferguson

unread,
Oct 10, 2012, 5:37:27 PM10/10/12
to codehaus-mojo-gwt-...@googlegroups.com
Hi,

Try:

mvn clean
mvn gwt:clean
mvn package (and/or install)

Cheers
Rob

Kiahu.com



--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/codehaus-mojo-gwt-maven-plugin-users/-/3kO-JzyM2lEJ.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users?hl=en.

Nicolas J.

unread,
Oct 12, 2012, 11:16:53 AM10/12/12
to codehaus-mojo-gwt-...@googlegroups.com
It seems to do the trick.

Thx
To post to this group, send email to codehaus-mojo-gwt-maven-plugin...@googlegroups.com.
To unsubscribe from this group, send email to codehaus-mojo-gwt-maven-plugin-users+unsubscribe@googlegroups.com.

Thomas Broyer

unread,
Oct 12, 2012, 1:38:49 PM10/12/12
to codehaus-mojo-gwt-...@googlegroups.com


On Friday, October 12, 2012 5:16:53 PM UTC+2, Nicolas J. wrote:
It seems to do the trick.

That's probably because your output folder for GWT is not in target/, so "mvn clean" doesn't clean it (if I understand correctly how the maven-clean-plugin works)
Reply all
Reply to author
Forward
0 new messages