GWT app development in teams

2010-07-22 Thread Ben
Hello all

I'm looking for best practices in developing GWT apps. Let's assume we
are 3-5 programmers working on a fairly big GWT app.
I could not find any straightforward information on this. Maybe
because it's absolutely clear for most developers or maybe there are
just too many possible solutions.

I know that this is not just a GWT specific question.

Anyways, back to our scenario. Let's assume its an GWT app with a
database behind, and using JAVA in the backend. Everything is working
on Linux basis.

My situation: I'm developing and debugging locally, then deploy
the .war file manually on my tomcat server. This works fine when
working alone. Now, a couple of friends want to join in. The whole
thing gets complex. What setup (e.g. server, software) would you use
to handle such a scenario?

Here are a couple thoughts I ran into:

1. Should each developer develop and debug locally (sharing files via
subversion) ? There is a big down-side on this. Each developer needs
to do the server configuration in order to keep the app running
locally. Is there an alternative?

2. How can one add server-side debug ability to the test server? On
the test server runs the app in hosted mode. How can errors, warnings
be stored and outputted to the developer? Is there a software or do
you work with error logs?

3. How can one export the files from a test server to a production
server? Is there any software which supports such function?

I'm programming for quite a while now, but I don't have any
experiences in programming together with other developers. So,
basically I would love to know anything how you guys develop GWT apps
in teams.

Please let me know if I shall be more precise.

Thanks for your tips!

benjamin

-- 
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-tool...@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: GWT app development in teams

2010-07-22 Thread Uberto Barbini
Hi Ben,

we're working in 10 people on a big gwt project.
Some people work in office, some remotely.
I think the problem in your scenario is

 My situation: I'm developing and debugging locally, then deploy
 the .war file manually on my tomcat server.

everything should be done automatically either by maven or by an ant task.

Then after the commit we have a CI server (hudson) that run tests and
deploy it in a preprod env.
All the debug is done locally.
We have 2 main scripts, one for run in hosted mode and another for run
on jetty. CI server deploy it on a Jboss configured like in
production.

hope this can help you.

cheers

Uberto

On Thu, Jul 22, 2010 at 2:14 PM, Ben benjamin.groehb...@gmail.com wrote:
 Hello all

 I'm looking for best practices in developing GWT apps. Let's assume we
 are 3-5 programmers working on a fairly big GWT app.
 I could not find any straightforward information on this. Maybe
 because it's absolutely clear for most developers or maybe there are
 just too many possible solutions.

 I know that this is not just a GWT specific question.

 Anyways, back to our scenario. Let's assume its an GWT app with a
 database behind, and using JAVA in the backend. Everything is working
 on Linux basis.

 My situation: I'm developing and debugging locally, then deploy
 the .war file manually on my tomcat server. This works fine when
 working alone. Now, a couple of friends want to join in. The whole
 thing gets complex. What setup (e.g. server, software) would you use
 to handle such a scenario?

 Here are a couple thoughts I ran into:

 1. Should each developer develop and debug locally (sharing files via
 subversion) ? There is a big down-side on this. Each developer needs
 to do the server configuration in order to keep the app running
 locally. Is there an alternative?

 2. How can one add server-side debug ability to the test server? On
 the test server runs the app in hosted mode. How can errors, warnings
 be stored and outputted to the developer? Is there a software or do
 you work with error logs?

 3. How can one export the files from a test server to a production
 server? Is there any software which supports such function?

 I'm programming for quite a while now, but I don't have any
 experiences in programming together with other developers. So,
 basically I would love to know anything how you guys develop GWT apps
 in teams.

 Please let me know if I shall be more precise.

 Thanks for your tips!

 benjamin

 --
 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-tool...@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.



-- 
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-tool...@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: GWT app development in teams

2010-07-22 Thread PhilBeaudoin
If it's a new project and you're not tied to a specific backend, you
could could consider deploying on AppEngine. This has been very
efficient for our team where every developer works remotely. AppEngine
offers a standardized built-in environment right in eclipse so
everybody can test locally with good confidence that the behavior will
be the same on the deployed version. We also use continuous deployment
to a (free) AppEngine account, our continuous integration solution is
TeamCity with a relatively simple ant script.

Other practices we use and I would recommend:
- DVCS (we use mercurial hosted on bitbucket)
- Use a highly decoupled architecture, consider an MVP framework. (we
use gwt-platform)
- Heavily unit test (we use JUnit4, mockito)
- Use DI to simplify the two above (we use GIN and Guice)
- Use integration testing (we're still experimenting tools in this
area)
- Asynchronous code reviews (rietveld works really well for us)
- Use UiBinder so that you can easily port HTML mockups to GWT.
- Find a good tool to monitor your dev process (we use AgileZen)

Cheers,

Philippe

On Jul 22, 8:59 am, Uberto Barbini ube...@ubiland.net wrote:
 Hi Ben,

 we're working in 10 people on a big gwt project.
 Some people work in office, some remotely.
 I think the problem in your scenario is

  My situation: I'm developing and debugging locally, then deploy
  the .war file manually on my tomcat server.

 everything should be done automatically either by maven or by an ant task.

 Then after the commit we have a CI server (hudson) that run tests and
 deploy it in a preprod env.
 All the debug is done locally.
 We have 2 main scripts, one for run in hosted mode and another for run
 on jetty. CI server deploy it on a Jboss configured like in
 production.

 hope this can help you.

 cheers

 Uberto



 On Thu, Jul 22, 2010 at 2:14 PM, Ben benjamin.groehb...@gmail.com wrote:
  Hello all

  I'm looking for best practices in developing GWT apps. Let's assume we
  are 3-5 programmers working on a fairly big GWT app.
  I could not find any straightforward information on this. Maybe
  because it's absolutely clear for most developers or maybe there are
  just too many possible solutions.

  I know that this is not just a GWT specific question.

  Anyways, back to our scenario. Let's assume its an GWT app with a
  database behind, and using JAVA in the backend. Everything is working
  on Linux basis.

  My situation: I'm developing and debugging locally, then deploy
  the .war file manually on my tomcat server. This works fine when
  working alone. Now, a couple of friends want to join in. The whole
  thing gets complex. What setup (e.g. server, software) would you use
  to handle such a scenario?

  Here are a couple thoughts I ran into:

  1. Should each developer develop and debug locally (sharing files via
  subversion) ? There is a big down-side on this. Each developer needs
  to do the server configuration in order to keep the app running
  locally. Is there an alternative?

  2. How can one add server-side debug ability to the test server? On
  the test server runs the app in hosted mode. How can errors, warnings
  be stored and outputted to the developer? Is there a software or do
  you work with error logs?

  3. How can one export the files from a test server to a production
  server? Is there any software which supports such function?

  I'm programming for quite a while now, but I don't have any
  experiences in programming together with other developers. So,
  basically I would love to know anything how you guys develop GWT apps
  in teams.

  Please let me know if I shall be more precise.

  Thanks for your tips!

  benjamin

  --
  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-tool...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-web-toolkit+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://groups.google.com/group/google-web-toolkit?hl=en.

-- 
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-tool...@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: GWT app development in teams

2010-07-22 Thread Flemming Boller
Hi Phil


What intgr. test tools are you evaluating?

I am evaluating selenium. I like selenium IDE, but I think it is a little
fragile.

/FLemming

On Thu, Jul 22, 2010 at 6:44 PM, PhilBeaudoin
philippe.beaud...@gmail.comwrote:

 If it's a new project and you're not tied to a specific backend, you
 could could consider deploying on AppEngine. This has been very
 efficient for our team where every developer works remotely. AppEngine
 offers a standardized built-in environment right in eclipse so
 everybody can test locally with good confidence that the behavior will
 be the same on the deployed version. We also use continuous deployment
 to a (free) AppEngine account, our continuous integration solution is
 TeamCity with a relatively simple ant script.

 Other practices we use and I would recommend:
 - DVCS (we use mercurial hosted on bitbucket)
 - Use a highly decoupled architecture, consider an MVP framework. (we
 use gwt-platform)
 - Heavily unit test (we use JUnit4, mockito)
 - Use DI to simplify the two above (we use GIN and Guice)
 - Use integration testing (we're still experimenting tools in this
 area)
 - Asynchronous code reviews (rietveld works really well for us)
 - Use UiBinder so that you can easily port HTML mockups to GWT.
 - Find a good tool to monitor your dev process (we use AgileZen)

 Cheers,

Philippe

 On Jul 22, 8:59 am, Uberto Barbini ube...@ubiland.net wrote:
  Hi Ben,
 
  we're working in 10 people on a big gwt project.
  Some people work in office, some remotely.
  I think the problem in your scenario is
 
   My situation: I'm developing and debugging locally, then deploy
   the .war file manually on my tomcat server.
 
  everything should be done automatically either by maven or by an ant
 task.
 
  Then after the commit we have a CI server (hudson) that run tests and
  deploy it in a preprod env.
  All the debug is done locally.
  We have 2 main scripts, one for run in hosted mode and another for run
  on jetty. CI server deploy it on a Jboss configured like in
  production.
 
  hope this can help you.
 
  cheers
 
  Uberto
 
 
 
  On Thu, Jul 22, 2010 at 2:14 PM, Ben benjamin.groehb...@gmail.com
 wrote:
   Hello all
 
   I'm looking for best practices in developing GWT apps. Let's assume we
   are 3-5 programmers working on a fairly big GWT app.
   I could not find any straightforward information on this. Maybe
   because it's absolutely clear for most developers or maybe there are
   just too many possible solutions.
 
   I know that this is not just a GWT specific question.
 
   Anyways, back to our scenario. Let's assume its an GWT app with a
   database behind, and using JAVA in the backend. Everything is working
   on Linux basis.
 
   My situation: I'm developing and debugging locally, then deploy
   the .war file manually on my tomcat server. This works fine when
   working alone. Now, a couple of friends want to join in. The whole
   thing gets complex. What setup (e.g. server, software) would you use
   to handle such a scenario?
 
   Here are a couple thoughts I ran into:
 
   1. Should each developer develop and debug locally (sharing files via
   subversion) ? There is a big down-side on this. Each developer needs
   to do the server configuration in order to keep the app running
   locally. Is there an alternative?
 
   2. How can one add server-side debug ability to the test server? On
   the test server runs the app in hosted mode. How can errors, warnings
   be stored and outputted to the developer? Is there a software or do
   you work with error logs?
 
   3. How can one export the files from a test server to a production
   server? Is there any software which supports such function?
 
   I'm programming for quite a while now, but I don't have any
   experiences in programming together with other developers. So,
   basically I would love to know anything how you guys develop GWT apps
   in teams.
 
   Please let me know if I shall be more precise.
 
   Thanks for your tips!
 
   benjamin
 
   --
   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-tool...@googlegroups.com.
   To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
   For more options, visit this group athttp://
 groups.google.com/group/google-web-toolkit?hl=en.

 --
 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-tool...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to 

Re: GWT app development in teams

2010-07-22 Thread Thomas Broyer


On 22 juil, 17:59, Uberto Barbini ube...@ubiland.net wrote:
 Hi Ben,

 we're working in 10 people on a big gwt project.
 Some people work in office, some remotely.
 I think the problem in your scenario is

  My situation: I'm developing and debugging locally, then deploy
  the .war file manually on my tomcat server.

 everything should be done automatically either by maven or by an ant task.

...or manually (by the project leader generally), but always based on
some revision on the SCM (we use Subversion), never on some local
working copy.

 Then after the commit we have a CI server (hudson) that run tests and
 deploy it in a preprod env.
 All the debug is done locally.

Same here in our new project. The old one was deployed manually: we
had a shell script on the test server that rm workingcopy, then svn
co, and finally ant build install (we used ant, we're now using
maven in our new project).

-- 
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-tool...@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.