Yep, that's what I meant. This is great! I'm starting several new
projects and I look forward to using gwt-maven to its full potential.
Thanks Charlie!

Regards,
Arthur Kalmenson

On Sep 10, 12:41 pm, Charlie Collins <[EMAIL PROTECTED]>
wrote:
> There is a separation on test cases, if that is what you mean?
>
> http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug...
>
> The GWTTestCase ones, which are only relative to CLIENT SIDE /
> translatable model and controller (not even UI frankly, but that is a
> point of debate with some), whether or not shared, use the "gwtFilter"
> property to be separated - the default is prefix "GwtTest*".  Standard
> test cases use suffix *Test".
>
> Not sure if that's what you mean, but that is how the testing support
> differentiates.
>
> On Sep 10, 9:25 am, Arthur Kalmenson <[EMAIL PROTECTED]> wrote:
>
> > Will there be separation between GWT code and regular Java code right?
> > This separation should especially be in the test cases.
>
> > There are a number of use cases where you have code that runs both on
> > the client and on the server (domain objects is one example). There
> > are also other use cases where there is client side code that is not
> > directly tied to GWT widgets (for example, following the MVC pattern
> > on the client side would only see GWT code in the View, but the
> > Controller and Model will be reusable).
>
> > In these cases, a separation between GWTTestCases and regular test
> > cases is a must. I frequently use TestNG, EasyMock and other testing
> > tools to test client side business logic that does not directly use
> > GWT widgets. If there is no separation between them in the archetype,
> > the GWT compiler will try to compile the non GWTTestCase code and
> > fail.
>
> > I don't know if I'm being very clear, let me know if it's confusing. I
> > can post this comment on the issue tracker as well (and maybe help out
> > too :P).
>
> > Regards,
> > Arthur Kalmenson
>
> > On Sep 9, 4:37 pm, Charlie Collins <[EMAIL PROTECTED]> wrote:
>
> > > Nope, it does not.  The archetype has been ancient for quite some
> > > time, but there is an issue in the tracker to update it (just haven't
> > > gotten to it).  Contributors and patches, etc, are welcome.
>
> > > On Sep 9, 2:22 pm, Jeff Bowman <[EMAIL PROTECTED]> wrote:
>
> > > > Does this include an updated version of the archetype?
>
> > > > On Sep 7, 5:33 am, Charlie Collins <[EMAIL PROTECTED]> wrote:
>
> > > > > New version, with a lot of refactoring, and fixes for many issues, is
> > > > > now available in the 
> > > > > repo:http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/com/totsp/gwt/mav...
>
> > > > > This version
> > > > > 1. Works with GWT 1.5.2 from central repo
> > > > > 2. Does the "automatic" mode processing differently, using the
> > > > > dependency plugin
> > > > > 3. Has rewritten GWTTestCase support (which does script writing like
> > > > > other mojos)
> > > > > 4. Has I18N support
> > > > > 5. Was refactored to remove a lot of duplicated code and use a few
> > > > > interfaces and abstract classes and such so it is easier to understand
> > > > > and work with when you are looking at the source
> > > > > 6. Addresses about 15 or so issues from the tracker
> > > > > 7. Does NOT supoort the bean generation stuff anymore (there were too
> > > > > many issues, and we no longer have a maintainer for that - so it is
> > > > > gone until further notice - if the maintainer comes back, or someone
> > > > > else wants to volunteer - and we address all the issues [see tracker]
> > > > > then it will be back).
>
> > > > > This version was based on all the work and input done in the recent
> > > > > refactoring 
> > > > > branch:http://groups.google.com/group/gwt-maven/browse_thread/thread/83664ca....
> > > > > Thanks to Mirko and Arthur, and others for help and testing, etc.
>
> > > > > Check out the 
> > > > > docs:http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug....
> > > > > (I am pretty proud of the docs ;) - we now have some that use the
> > > > > Maven standard, with all goals and properties, source xref, javadocs,
> > > > > and from there we expand on what it provides a bit.)
>
> > > > > Also the samples are updated to use the new 
> > > > > version:http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-plu......
>
> > > > > If you find issues, please note them here and via the tracker.
>
> > > > > thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"gwt-maven" 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/gwt-maven?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to