[
https://jira.codehaus.org/browse/MGWT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293651#comment-293651
]
Dieter König commented on MGWT-297:
-----------------------------------
I would like to explain the usecase.
We have just a normal java project which is already used in normal java
applications. Now we would like to share some parts of this code for gwt
applications. Well, let's say we refactor the project so now we have two main
packages "shared" and "java". That project is already generating two jars
(normal one and sources). Let's say we place the gwt.xml in that project
defining shared package as gwt source code. Now the last missing step is the
validation of the code in the shared-package to be gwt compatible.
The default usecase would be that the validate goal (which i would prefer to
have in the pre-package phase) will fail if the declared gwt source code (i.e.
"shared" package) is not gwt compatible.
The advantage would be that lots of java projects out there could make their
code verified for gwt usage and still remain just a normal java project.
-----------
With actual implementation just builds at the end of the chain of projects can
fail... (the ones where gwt-compile happens) which is toooo late
> Add a "validate" goal, almost equivalent to gwt:compile with -validateOnly
> --------------------------------------------------------------------------
>
> Key: MGWT-297
> URL: https://jira.codehaus.org/browse/MGWT-297
> Project: Maven 2.x GWT Plugin
> Issue Type: New Feature
> Affects Versions: 2.3.0
> Reporter: Thomas Broyer
>
> When developping "GWT libraries", you can call the GWT Compiler with
> {{\-validateOnly}} to check that your GWT modules are OK (check for "compile
> errors" -- bad includes/excludes on {{<source>}} paths, missing
> {{<super-source>}}, etc. -- , missing {{<inherits/>}}, typos in rebind rules,
> etc.)
> It'd be handy to have a {{gwt:validate}} goal, probably bound by default to
> the "verify" phase.
> The {{gwt:compile}} goal cannot be used in most cases as a "library module"
> is unlikely to include an entry-point, and {{gwt:compile}} skips when that's
> the case (even with {{-Dgwt.compiler.force=true}})
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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