[jbosstools-issues] [JBoss JIRA] (JBIDE-12048) Maven GWT compiler seem to assume projects that uses gwt-compiler is always a WTP project

[Guido Bonazza (JIRA)]

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

Guido Bonazza commented on JBIDE-12048:
---------------------------------------

I think that the GWTProjectConfigurator should handle the gwt-maven-plugin on a goal-per-goal base: the generateAsync goal should at least add the target/generated-sources/gwt folder to the build path, and it doesn't depend on the project's webcontent folder (it makes sense in jar projects); the webcontent folder only affects the compile goal, I think, but I don't really know what all the other goals would need.
                
> Maven GWT compiler seem to assume projects that uses gwt-compiler is always a WTP project
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12048
>                 URL: https://issues.jboss.org/browse/JBIDE-12048
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: GWT, maven
>            Reporter: Max Rydahl Andersen
>            Assignee: Denis Golovin
>            Priority: Critical
>             Fix For: 3.3.0.CR1, 3.3.1
>
>         Attachments: gwt-utility-example.zip
>
>
> User found that if he uses gwt-compiler-plugin and the project does not have wtp on it we fail hard.
> Not sure what we can do besides just fail silently here or is there a way to survive without knowing the webcontent folder ?

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