If you know enough to start writing generators, it almost certainly is not 
a concern - you are probably also careful with which GWT version you are 
using as well as which gwt-m-p version. A problem can occur if more than 
one version of gwt-dev is present on the classpath, such as a mistakenly 
declared copy in your dependencies and the copy that gwt-m-p automatically 
pulls in. Provided both versions are the same or care is taken to ensure 
that gwt-m-p uses the same dependency, there is no issue.

See 
http://mojo.codehaus.org/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html
 
for how to configure your project to allow for different GWT SDK version 
from the maven plugin. I typically use two different properties, one for 
gwt.version, and a second for gwt.plugin.version with this strategy to 
allow them fall out of sync in a safe way.

On Friday, February 7, 2014 11:09:23 AM UTC-6, Gilberto Torrezan Filho 
wrote:
>
> Hi,
>
> I'm using GWT 2.6.0 with Maven, using the gwt-maven-plugin, and in my 
> project I have some auto generated classes (using the <generated-with> 
> directive on Module.gwt.xml). The generator is a subclass of 
> com.google.gwt.core.ext.Generator.
>
> The problem is: every time I build my project, Maven emits a warning:
>
> [WARNING] Don't declare gwt-dev as a project dependency. This may 
>> introduce complex dependency conflicts
>>
>
> ... but I have to declare gwt-dev as dependency, since I need it to 
> compile my code generator.
>
> I never faced any conflict - maybe because I'm declaring gwt-dev with the 
> "provided" scope, avoiding it to be part of the generated war. So, in this 
> scenario, is that warning still accurate? Is there any other way to avoid 
> it (while still having the code generators)?
>
> Thanks.
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to