[
http://jira.codehaus.org/browse/MGWT-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261589#action_261589
]
Jean Helou commented on MGWT-281:
---------------------------------
I think this is a slightly different problem actually.
GEP _does_ supports multiple source folders however m2eclipse sets an exclusion
filter : '**' on the resources folders of the java build path in eclipse (see
attached screen shot).
Because of this, even if the resources folders are considered as source folders
and get the small package icon, their content is in fact excluded from the
classpath and folders don't get resolved as packages...
If you remove the exclusion filter, GEP finds the modules.
According to the issue I linked to in GEP, it is not safe to remove these
exclusion filters because eclipse may overwrite resources processed by maven.
Unfortunately a real solution seems to imply changing either m2eclipse or
eclipse or GEP or all of these.
> Eclipse build directory setup is incorrect
> ------------------------------------------
>
> Key: MGWT-281
> URL: http://jira.codehaus.org/browse/MGWT-281
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.2.0
> Environment: eclipse 3.6, jdk 1.6, win7 64b, Google plugin for
> eclipse 3.6, Google Web toolit SDK 2.2.0,m2eclipse 0.12.1
> Reporter: Jean Helou
> Priority: Minor
>
> I followed
> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html .
> Then in a fresh workspace with the above configuration (latest version of
> everything I could find) right click-> import -> Maven -> Existing Maven
> project.
> Once the project is fully imported, the Google plugin doesn't see the Module
> file. Try right clicking on the project -> google -> Gwt compile and the
> module list is empty
> Move the Module file to src/main/java/${package}/ instead of
> src/main/resources/${package} and the plugin finds the modules again.
> A lookup for this bug in the gwt issue tracked yields
> http://code.google.com/p/google-web-toolkit/issues/detail?id=3759 in which it
> is stated that for the plugin to be able to see the file, one needs to remove
> the ** regexp set in the "excluded" section of the src/main/resources/ in the
> java build path.
> Since the Java Build path is maintained by m2eclipse this workaround only
> works until m2eclipse updates the project configuration.
> I am not exactly sure how to configure my pom to handle this,and I would
> expect it to be automatically setup when using archetype genertion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
