[jbosstools-issues] [JBoss JIRA] (JBIDE-11244) Auto-discover all the modules and add them to the configuration on GWT project import
[
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 ?
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,
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