Re: Project Structure in GWT-2.0

2009-09-30 Thread Iain Shigeoka

Agreed. I certainly am not advocating for google to change their own  
build system for GWT, just that GWT be friendlier to teams that do use  
Maven for our own projects. As DPeters states, the biggest and most  
painful aspect of the new war design is the mixing of source and  
compiled classes. Simply having the compiled classes be a separately  
configured location from the source would allow those of us using  
Maven or any other "clean source tree" file organization build process  
work much smoother with GWT.

-iain

On Sep 30, 2009, at 8:04 AM, D Peters wrote:

> Yes.  I am not suggesting that GWT change their source tree to the /
> src/main type structure that Maven requires.  IMHO it should be
> Maven's responsibilty to be flexible to difference source tree
> structures.  However, the concept of "keeping the source tree clean"
> is an important one that GWT's build process should subscribe to..
> Otherwise it will always be a pain in the butt when setting up your
> build scripts -- whatever tool that you use...


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: Project Structure in GWT-2.0

2009-09-29 Thread Iain Shigeoka

+1 Maven friendly is ideal. Less ideal but better than current is  
separation of source and compiled code as the original poster mentioned.

-iain

On Sep 29, 2009, at 9:02 AM, Michał Sędzielewski wrote:

>
> I agree, it would be nice to have maven structure in GWT 2.0
>
> On 28 Wrz, 15:45, logicpeters  wrote:
>> Can anyone tell me if there are plans to rework the way the  
>> currentGWTproject structure is configured for2.0?  Mxing the source  
>> and
>> compiled code in the /war folder has been a real pain in the butt for
>> build scripts and source control.  I've been trying to "mavenize" our
>> project, and find the various solutions to be un-elegant hacks that
>> wind up confusing the structure even more.
> >


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---



Re: Does GWT work in Snow Leopard?

2009-09-17 Thread Iain Shigeoka

Thanks Sumit. That's a great news.

For those of you who can't wait for the official patch release, I've
rebuilt the gwt-dev-mac.jar file from a checkout of the 1.7.0 tag.
I've made a very minor edit to the BootStrapPlatform.java file (diff
shown below) to check for 32-bit-ness rather than 1.5-ness. In order
to use this on Snow Leopard with 1.6 simply add the "-d32" option to
your java command line to use the 32-bit version of the jvm. Note that
since this is a temporary work around and a convenience for building
your own 1.7.0 patch I'm only going to keep the link active until the
official GWT patch is out. Let me know if anyone runs into any
problems.

http://www.messaginglogic.com/gwt-dev-mac.jar

-iain

ion $ svn diff BootStrapPlatform.java
Index: BootStrapPlatform.java
===
--- BootStrapPlatform.java  (revision 6146)
+++ BootStrapPlatform.java  (working copy)
@@ -69,8 +69,8 @@
  * The following check must be made before attempting to
initialize Safari,
  * or we'll fail with an less-than-helpful UnsatisfiedLinkError.
  */
-if (!isJava5()) {
-  System.err.println("You must use a Java 1.5 runtime to use GWT
Hosted Mode on Mac OS X.");
+if (!isJava32()) {
+  System.err.println("You must use a Java 32-bit runtime to use
GWT Hosted Mode on Mac OS X.");
   System.exit(-1);
 }

@@ -111,11 +111,11 @@
   }

   /**
-   * Determine if we're using the Java 1.5 runtime, since the 1.6
runtime is
+   * Determine if we're using the Java 32-bit runtime, since the 1.6
runtime can be
* 64-bit.
*/
-  private static boolean isJava5() {
-return System.getProperty("java.version").startsWith("1.5");
+  private static boolean isJava32() {
+return System.getProperty("sun.arch.data.model").equals("32");
   }

   /**


On Sep 14, 5:33 pm, Sumit Chandel  wrote:
> Hi All,
> For those of you who have been running into problems using GWT 1.7 with Snow
> Leopard, please accept our humble apologies.
>
> We are working on getting a GWT 1.7 point release out that will fix this
> issue so that you may use Snow Leopard with the JDK 1.6 32-bit libraries
> without having to tweak your OS settings.
>
> Cheers,
> -Sumit Chandel
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---