And hopefully (Nir mentioned this prior), there will be a way to
exclude a specific set of classes via some 'ant matcher' from the
module. We keep the path the same and it looks like GWT looks at both
directories and throws errors which I don't believe affect execution,
but are confusing:
Validating newly compiled units
[ERROR] Errors in 'file:/C:/work/bigproject/src/test/java/com/
example/gwt/client/ui/SampleUiTest.java'
[ERROR] Line 43: No source code is available for type
org.mockito.Mockito; did you forget to inherit a required module?
[ERROR] Line 48: No source code is available for type
org.mockito.Matchers; did you forget to inherit a required module?
In our module we have:
<source path="client"></source>
<source path="common"></source>
where client holds the UI code and common holds DTO classes between
the RPC Server and Client. The common is probably redundant to a dto
package, but nevertheless. If I move my test out of the package
specified by client, the error goes away.
gwt compile or specify ant expressions for gwt compile. Our convention
(and I believe a maven convention) is for test cases to exist in the
src/test tree with the same path as the class under test in the tree:
src/main.
Hopefully that makes sense.
Brian
On Feb 4, 12:55 pm, bkbonner <[email protected]> wrote:
> Keith, are you going to give the folks who replied to your message
> some sort of thoughts on what you're going to implement and hopefully
> let us try it before you end up releasing the next release of the
> plugin?
>
> Brian
>
> On Jan 13, 11:35 am, Keith Platfoot <[email protected]> wrote:
>
>
>
> > Hi folks,
>
> > For the next release of the Google Plugin for Eclipse, we're planning on
> > making a few tweaks to make life easier for Maven users. That's right: we've
> > seen the stars on the issue tracker, and have decided it's time to act. I
> > would say, "we feel your pain", but the problem is, we don't. Which is to
> > say, nobody on the plugin team actually uses Maven (everybody around here
> > uses Ant). However, I've been researching Maven to determine exactly what
> > changes we should make to allow it to work more seamlessly with the Google
> > Eclipse Plugin. I've read the relevant issues and groups postings, so I
> > think I have a rough idea of what needs to happen. However, before we go and
> > make any changes, I wanted to ask for the community's advice. So, here are
> > some questions for you.
>
> > What is the typical workflow of a GWT developer using Maven?
>
> > I've installed Maven and the gwt-maven-plugin 1.2-SNAPSHOT and managed to
> > create a GWT 2.0 app with the provided archetype. After some tweaking, I'm
> > able to GWT compile, debug with Eclipse (though not via our Web App launch
> > configuration), create a WAR, etc. However, I'm more interested in how you
> > all
> > are doing things. For example:
>
> > How do you...
>
> > - Create a new project?
> > - Perform GWT compiles?
> > - Debug with Eclipse?
> > - Run your tests?
> > - Create a WAR for deployment?
>
> > What specific pain points do Maven users run into when using the Google
> > plugin?
>
> > I know one major obstacle is that our plugin currently treats the war
> > directory as both an input (e.g. static resources, WEB-INF/lib,
> > WEB-INF/web.xml) and output (WEB-INF/classes, GWT artifacts like nocache.js
> > and hosted.html) . Maven convention, however, says that /src/main/webapp
> > should be input only, which means that hosted mode (or development mode, in
> > GWT 2.0) needs to run from a staging directory (e.g. gwt:run creates a /war
> > folder on demand). This mismatch results in the plugin creating spurious
> > validation errors and breaks our Web App launch configuration.
>
> > Another incompatibility is that Maven projects depend on the GWT Jars in the
> > Maven repo, whereas our plugin expects to always find a GWT SDK library on
> > the classpath.
>
> > Are my descriptions of these pain points accurate? If so, one possible
> > solution would be for the plugin to allow the definition of an input war
> > directory (e.g. src/main/webapp) separate from a launch-time staging
> > directory, and for us to relax the requirement that all GWT projects must
> > have a GWT SDK library. So tell me: would these changes adequately reduce
> > the friction between Maven and the Google plugin?
>
> > Also, are there other problems Maven users are running into when using the
> > plugin?
>
> > Thanks in advance for all feedback,
>
> > Keith, on behalf of the Google Plugin for Eclipse team
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
