[jbosstools-issues] [JBoss JIRA] (JBIDE-11236) gwt-kitchensink not working when deployed from within JBT

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677716#comment-12677716 ] 

Snjezana Peco commented on JBIDE-11236:
---------------------------------------

I can't reproduce the OOME  when using 

- Linux and Windows 32-bit
- gwt 2.5.1/2.5.2, m2e 1.0.200 (the versions included in JBT 3.3.0.Beta/JBDS 5.0.0.Beta)
- org.jboss.errai.archetypes:kitchesink-quickstart:2.0.Beta3
- the default JBDS JVM settings
- incremental and full build
- publishing to JBoss AS 7.1.1.GA

There is not any memory leak either in m2e or in gwt when building the project with the compile goal.
The JBDS memory usage always returns to around 130MB.

Maybe you have some other problem in your environment that causes the OOME.

BTW,
In order the gwt.compile goal not to be called on every Save operation, it is enough to replace the following in the m2e plugin:

{code}
<action>
     <execute />
</action>
{code}

with

{code}
<action>
    <execute >
        <runOnIncremental>false</runOnIncremental>
      </execute >
</action>
{code}

The gwt:compile operation will be called only when calling a full build (Project>Clean).
The user will have to call full build (Project>Clean) whenever he changes the GWT code. Sometimes, he will also have to call Project Refresh.

The complete m2e plugin declaration I have tested is the following:

{code}
<!-- m2e (Maven integration for Eclipse) requires the following configuration -->
        <plugin>
          <groupId>org.eclipse.m2e</groupId>
          <artifactId>lifecycle-mapping</artifactId>
          <version>1.0.0</version>
          <configuration>
            <lifecycleMappingMetadata>
              <pluginExecutions>
                <pluginExecution>
                  <pluginExecutionFilter>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>gwt-maven-plugin</artifactId>
                    <versionRange>[2.3.0,)</versionRange>
                    <goals>
                      <goal>resources</goal>
                      <goal>compile</goal>
                    </goals>
                  </pluginExecutionFilter>
                  <action>
                	<execute >
                  		<runOnIncremental>false</runOnIncremental>
                	</execute >
              	  </action>
                </pluginExecution>
              </pluginExecutions>
            </lifecycleMappingMetadata>
          </configuration>
        </plugin>
{code}



                
> gwt-kitchensink not working when deployed from within JBT
> ---------------------------------------------------------
>
>                 Key: JBIDE-11236
>                 URL: https://issues.jboss.org/browse/JBIDE-11236
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: project-examples
>    Affects Versions: 3.3.0.Beta1
>         Environment: JBT 3.3.0.Beta1e on eclipseEE indigo SR2
> Fedora 16
> Oracle java 1.7.0_02-b13 64b
>            Reporter: Radim Hopp
>            Assignee: Fred Bricon
>             Fix For: 3.3.0.Beta1
>
>         Attachments: gwt-kitchensink.png
>
>
> GWT Web Project is not working, when deployed from within JBDS or JBT (using steps described in README.md).
> When deployed, only header, footed and the right "Find out more" panel is shown.
> When deployed from command line using `mvn package` -> `mvn jboss-as:deploy` everything is working as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira