[jbosstools-issues] [JBoss JIRA] (JBIDE-11244) Auto-discover all the modules and add them to the configuration on GWT project import

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-11244:
---------------------------------------

Here are several other use cases:

# Configuration for several Entry Point Modules:
{code}<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>gwt-maven-plugin</artifactId>
  <version>${version.org.codehaus.mojo.gwt.maven.plugin}</version>
  <configuration>
   <inplace>true</inplace>
   <logLevel>INFO</logLevel>
   <extraJvmArgs>-Xmx512m</extraJvmArgs>
   <!-- Configure GWT's development mode (formerly known as hosted 
        mode) to not start the default server (embedded jetty), but to download the 
        HTML host page from the configured runTarget. -->
   <noServer>true</noServer>
   <runTarget>http://localhost:8080/gwt-kitchensink2/KitchenSink.html</runTarget>
   <modules>
      <module>org.jboss.tools.gwt.kitchensink.KitchenSink</module>
      <module>org.jboss.tools.gwt.kitchensink.KitchenSink1</module>
   </modules>
  </configuration>
<plugin>{code}

# Wrong configurations that doesn't reported by m2e and works for maven build. It just pick ups module node first no matter where it is before or after modules node. Both configurations below leads to org.jboss.tools.gwt.kitchensink.KitchenSink being compiled. Which means module declaration has priority over modules

{code}<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>gwt-maven-plugin</artifactId>
  <version>${version.org.codehaus.mojo.gwt.maven.plugin}</version>
  <configuration>
   <inplace>true</inplace>
   <logLevel>INFO</logLevel>
   <extraJvmArgs>-Xmx512m</extraJvmArgs>
   <!-- Configure GWT's development mode (formerly known as hosted 
        mode) to not start the default server (embedded jetty), but to download the 
        HTML host page from the configured runTarget. -->
   <noServer>true</noServer>
   <runTarget>http://localhost:8080/gwt-kitchensink2/KitchenSink.html</runTarget>
   <module>org.jboss.tools.gwt.kitchensink.KitchenSink</module>
   <modules>
      <module>org.jboss.tools.gwt.kitchensink.KitchenSink1</module>
      <module>org.jboss.tools.gwt.kitchensink.KitchenSink2</module>
   </modules>
  </configuration>
<plugin>{code}

{code}<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>gwt-maven-plugin</artifactId>
  <version>${version.org.codehaus.mojo.gwt.maven.plugin}</version>
  <configuration>
   <inplace>true</inplace>
   <logLevel>INFO</logLevel>
   <extraJvmArgs>-Xmx512m</extraJvmArgs>
   <!-- Configure GWT's development mode (formerly known as hosted 
        mode) to not start the default server (embedded jetty), but to download the 
        HTML host page from the configured runTarget. -->
   <noServer>true</noServer>
   <runTarget>http://localhost:8080/gwt-kitchensink2/KitchenSink.html</runTarget>
   <modules>
      <module>org.jboss.tools.gwt.kitchensink.KitchenSink1</module>
      <module>org.jboss.tools.gwt.kitchensink.KitchenSink2</module>
   </modules>
   <module>org.jboss.tools.gwt.kitchensink.KitchenSink</module>
  </configuration>
<plugin>{code}

                
> Auto-discover all the modules and add them to the configuration on GWT project import
> -------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11244
>                 URL: https://issues.jboss.org/browse/JBIDE-11244
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: GWT, maven
>            Reporter: Jonathan Fuerth
>            Assignee: Denis Golovin
>              Labels: new_and_noteworthy
>             Fix For: 3.3.0.Beta3
>
>         Attachments: EntryPointConfiguration.png, JBIDE-11244.patch, JBIDE-11244.patch, MavenIntegrationPrefsAfterPatch.png
>
>
> You can see why this would be desirable at 2:45 of the screencast at http://www.screencast.com/t/sFmXVlaBUvW
> !EntryPointConfiguration.png!
> Note that Errai Maven builds are configured to auto-discover modules too, so this would match existing users' expectations.

--
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