[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-11244: ---------------------------------- Attachment: EntryPointConfiguration.png -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-11244: ---------------------------------- Description: 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. was: You can see why this would be desirable at 2:45 of the screencast at http://www.screencast.com/t/sFmXVlaBUvW !EntryPointConfiguration.png|thumbnail! 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-11244: --------------------------------------- Added configurator plugin and feature the same way it is done for cdi. Attached patch should be applied first to let enable/disable configuration. -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11244: --------------------------------------------- Interesting ;) how does this play with GPE's own configurator ? How does it know what to set ? -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11244: --------------------------------------------- Asking the user every time is not going to be good. Doesn't the gwt-maven-plugin need this info too somehow ? How is it finding these ? btw. could this configurator also set the output directory to be aligned so mvn and eclipse compiles to the same output instead of duplicating files ? -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11244: --------------------------------------------- Yes, it was about JBIDE-11224 :) About the modules I googled a bit and found http://code.google.com/p/googleappengine/issues/detail?id=1597. Looks like GPE actually does scan but with m2e it gets confused - worth looking at ? More over seems that http://mojo.codehaus.org/gwt-maven-plugin/compile-mojo.html describes that if neither <module> nor <modules> are present on gwt-compiler then autodiscover is what should be implied. Can we use that as the way to control it ? i.e. first rev only scans for all gwt.xml if no module nor modules listed ? and then the "perfect" one uses info found in module/modules ? -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-11244 at 4/10/12 5:40 PM: ---------------------------------------------------------------- For Burr's demo adding {code}<module>org.jboss.tools.gwt.kitchensink.KitchenSink</module>{code} in pom.xml into gwt-maven-plugin configuration below {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> </configuration> <plugin>{code} would eliminate extra configuration in GWT preferences for the project was (Author: dgolovin): For Burr's demo adding {code}<module>org.jboss.tools.gwt.kitchensink.KitchenSink</module>{code} in pom.xml into gwt-maven-plugin configuration below {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> </configuration>{code} would eliminate extra configuration in GWT preferences for the project -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-11244: --------------------------------------- Since build in demo is done by maven, it is proposed fix for archetype. If it is configured that way there would be no issue reported and demo would work without additional configuration in eclipse. -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-11244: --------------------------------------- yes, it looks like having module configured in gwt-maven-plugin fixes the issue without gwt-m2e configurator. But I still need to do some tests. I've just installed Abridged JBossTools 3.3.0.Beta2. It means I have no Google plugins installed and no gwt-m2e configurator, but GWT-web-project just works without any additional configuration in pom.xml or in project preferences. I wonder if there is conflict between tools involved: GWT Integration, m2e and GDT. -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-11244: ---------------------------------- Attachment: JBIDE-11244.patch -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] 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} -- 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

[ https://issues.jboss.org/browse/JBIDE-11244?page=com.atlassian.jira.plugi... ] Isaac Rooskov updated JBIDE-11244: ---------------------------------- Release Notes Docs Status: Not Required Writer: irooskov Release note not required as GWT support will be documented as a new feature/component for JBDS 5 -- 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