GWT goes completely open source
Dan Morrill
(http://googlewebtoolkit.blogspot.com/2006/12/gwt-13-release-candidate-is-100-open_12.html),
but if you haven't, the GWT team is very excited to let you know that
GWT is now 100% open source! This means that the core
Java-to-JavaScript compiler and the hosted mode debugger are now
available under the same Apache 2.0 license as the user libraries.
If you'd like to take a look behind the scenes of GWT, you can check
out the Making GWT Better guide
(http://code.google.com/webtoolkit/makinggwtbetter.html), but this
message will help you get started as well.
First things first: To coincide with the source code release, we have
released version 1.3 Release Candidate 1 of GWT. This release is
functionally the same as the previous one, but we wanted to keep our
source and binary releases in sync.
Next, we've created a contributor-focused Google Group. The GWT
Developer Forum you're all reading this message on isn't going away;
the community you've come to rely on to talk through any issues you
have using GWT will still be here. The new group,
Google-Web-Toolkit-Contributors
(http://groups.google.com/group/Google-Web-Toolkit-Contributors), is
intended for people who are interested in contributing ideas or code
to the internals of GWT.
Since GWT is now completely open source, the GWT Issue Tracker
(http://code.google.com/p/google-web-toolkit/issues/list) takes on a
renewed importance. The GWT committers will monitor the Issue Tracker
closely, keep it up to date, and use it to track issues and
milestones. Users will be able to use it to get a sense of current
developer priorities, as well as find open bugs.
Great documentation, of course, is just as important as great
software. That's why we've also released all the GWT documentation on
the GWT web site under a Creative Commons license. This means that you
have freedom to improve and redistribute the GWT documentation similar
to the freedom you now have to improve and redistribute GWT itself!
More information is available at the Google Code Policies page
(http://code.google.com/policies.html).
Finally, we hope that many of you will join us in improving GWT. If
you're interested, you will find all the details about how to
contribute at the Making GWT Better page
(http://code.google.com/webtoolkit/makinggwtbetter.html).
Our community is the best! Thanks for using GWT, and we hope you have
as much fun using (and improving) it as we did developing it!
Luciano Broussal
Thank you Google for last part of the fuse !!!!!
Take care prototype , dojo and others. GWT is the turtle for the
Ajaxian reports, but not more for a long time now !!!!
http://ajaxian.com/archives/ajaxiancom-2006-survey-results
Luciano Broussal
Tucu
but I had doubts about using it in a real product. Open sourcing it has
removed the doubts.
One comment for the GWT team: GWT does not build on OS X unless you
make a couple of small changes to the build files. The build files try
to detect if JAVA_HOME is set to a JRE or a JDK by looking for
tools.jar; in OS X tools.jar does not exist.
Diego Salazar
basstech
Tucu - Exactly what changes need to be made in order to compile on OS X?
Tucu
does not exist in OS X and this check is not necessary.
- In trunk/doc/build.xml comment out line 32
- In trunk/build-tools/doctool/build.xml comment out line 6
I am sure there are better ways to fix the problem, but this one works
for me.
Tucu
moxie
~= Chris =~
mP
the then opened sourced stuff is finally released. And here I thought
the issue tracker was purely for entertainment purposes :)
wangzx
in the WEB world.
Zhou Renjian
I think this action will generate more Java-to-JavaScript compiler
detail discussions and give birth to more innovational ideas.
--
Regards,
Zhou Renjian
http://j2s.sourceforge.net/
Java2Script: Bridge of RCP to RIA
Reusing Java codes and tools into JavaScript
rk
Sanat Gersappa
hlima
Can't wait to download the source and start contributing :)
I'm glad of being part of this community.
Prakash
phaggood
> we've also released all the GWT documentation on
> the GWT web site under a Creative Commons license.
And my first request is that someone, ANYONE who's got a consistent
method for creating WARs that take a working GWT app that compiles and
works fine in the hosted server to an external Tomcat server, please
please write a howto and put it in the docs.
Dan Morrill
I'm already working on one, as it happens.
The open source/Creative Commons/1.3 release unfortunately contains no new documentation. However, one of the things I'm working on is documentation issues, and this is definitely a topic on the list. The docs aren't ready yet, but should be fairly soon.
In the meantime, below is an 'ant' target that I use to do exactly what you describe. Unfortunately it's not a part of the .ant.xml files generated by the tools, so you'll have to add it, but perhaps it will be useful to you. It is not ideal (it runs the compiler itself via a process fork where it would be better to have a custom ant task do it -- primarily b/c it was easiest this way) but it should work with 1.2 and 1.3.
It assumes you have a subdirectory called "war" where it is to put a live copy of the WAR files prior to JAR-ing. Also watch out for the hard-coded JAR paths.
<target name="war">
<mkdir dir="war/WEB-INF/classes"/>
<mkdir dir="war-build"/>
<mkdir dir="test"/>
<javac srcdir="src:test" destdir="war/WEB-INF/classes" includes="**" debug="on" debuglevel="lines,vars,source" source=" 1.5">
<classpath refid="project.class.path"/>
</javac>
<java classname="com.google.gwt.dev.GWTCompiler" fork="yes">
<classpath>
<pathelement path="${java.class.path}/"/>
<pathelement path="src"/>
<pathelement path="/opt/gwt/gwt-user.jar"/>
<pathelement path="/opt/gwt/gwt- dev-linux.jar"/>
</classpath>
<!-- <jvmarg value="-XstartOnFirstThread"/> -->
<arg value="-out"/>
<arg value="war-build"/>
<arg value="com.google.apppkg.AppName"/>
</java>
<copy todir="war">
<fileset dir="war-build/com.google.apppkg.AppName"/>
</copy>
<delete dir="war-build"/>
<jar destfile="AppName.war">
<fileset dir="war" includes="**"/>
</jar>
</target>
- Dan Morrill
Chad Bourque
I have just thrown together a quick step-by-step for doing this without Maven or Ant tools. This is how I do it. I think all the steps are there. If anyone tries to follow this and finds that it is missing anything, please let me know.
http://charisacademy.com/GWT/createwar.htm
Thanks,
Chad
There are two types of people in the world:
* Those who need closure
Luciano Broussal
differents configuration like for J2EE AppFuse project?
(java world)
GWT + external server
GWT + external server + hibernate + spring
GWT + external server + acegi security
(lamp world )
GWT + external server + PHP + JSON
(Rails + ruby world)
....
(flash world)
....
etc
I'm interested by this kind of contribution task but i'm really busy
for now. (next year?) if you are interested by a gwt environement
configuration tool? let us know!!!
Wainting that do a google search to see what is AppFuse if you don't
know it for J2EE applications.
Luciano Broussal.
Luciano Broussal
I use some ant task to auto complete that close to the one posted by
Dan:)
i will post it but have to clean it before from specifics things to
my projects :)
Luciano.
rusty
about this announcement: now I have an easy comeback to all those
trolls that say 'but the compiler is closed source, and Google will
just take you for a ride' and your list of Tier 1 things to do (down
the bottom of this page
http://code.google.com/webtoolkit/makinggwtbetter.html).
thanks again,
Rusty
Abdel
phaggood
after Fri - big project due then)
Rahul
The ant task mentioned by you is fine as long as one has single module
to compile. What if we will have more than one module, which is the
case in most of the enterprise level apps. In that case it is not a
promising solution to compile it through this task as it is taking very
long time and it it is having few redundancies.
For details refer to:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/043fbeed877eb48f
Thanks,
Rahul
Luciano Broussal
I think you don't need war stage most of the time your developping the
product.
It is just needed to deploy on cruise control server for testing (done
when you commit your modification in the repository) and for release
delivery stage.
We have to work in explode project most of the time if you want save
your time :)
Luciano
Rahul
I agree with you but the problem I have mentioned above is not in
creating war file. Rather it is in compiling EntryPoint classes to
javascript code. Every time I am recompiling unchanged EntryPoint
class, GWT compiler is translating it to javascript code and thus
consuming time.
Futher in any enterprise application you have many EntryPoint classes
for respective display pages. But GWT invokes GWTCompiler for each and
every EntryPoint class separately and thus adds to build time.
Rahul
Konstantin Scheglov
> Futher in any enterprise application you have many EntryPoint classes
> for respective display pages. But GWT invokes GWTCompiler for each and
> every EntryPoint class separately and thus adds to build time.
Wrong. When you run GWTCompiler you should specify module, not
EntryPoint. You can have several EntryPoint's in one GWT module.
--
Konstantin Scheglov
http://www.instantiations.com/gwtdesigner/ - WYSIWYG GUI builder for GWT
Rahul
module but in my case one HTML file is referring to one GWT module
which in turn refer to one EntryPoint class, so I cannot put more than
one EntryPoint class in a single Module. For example,
LoginPage.html ---REFERS TO---> loginPage.gwt.xml ---CONTAINS REFERENCE
TO---> LoginEntryPoint.java
DetailsPage.html ---REFERS TO---> detailsPage.gwt.xml ---CONTAINS
REFERENCE TO---> DetailsEntryPoint.java
In the above example, I cannot put both the EntryPoint classes in same
module as both modules refer to different pages.
Rahul
Andy Luo
rzorzorzo
The last hurdle for using GWT has thus been removed.
Thanks to all the GWT developers. This is a great toolkit.
- Ron
Josh Long
Now, to see about that maven support! :-)
Thanks again,
Josh
recht
Hi
This is exactly why I wrote an ant task for gwt - it can compile all
modules in a single task. Find it at http://braindump.dk/tech/
//Joakim
Luciano Broussal
So if you are a eclipse user. You can add predefined automatic build
tasks assigned to each sub module (on task by entry point) entry point
and this way eclipse will launch only the build for the sub module
entry point for which the source code is suspected to have been
change!!!!!
Best regards
Luciano Broussal
--
http://www.gwtwindowmanager.org