This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
i was asked by my friend to do create a web application using java (i am going to use grails). I have no problem with grails, but I got a problem when I need to do an update. His office was located on far far away from my city. So I have to send a war file everytime I did an update. They have internet but not connected to their application server ... so I have to send via email.
the problem is, war is quite big (about 25 MB) to be send via email... I don't want to send all of them if I just add/update an class. Is there any effective ways to send update (just the class) and I wish it looks like an installshield ...
You should look into setting up a source control repository that you both can access. Not only will this help keep backups of all your code and make rolling back changes easier, but then you can simply change your one class, commit it to source control, and your friend can pull it down and deploy it.
Marc's idea is probably the best, but if you cannot set up a common source control system here is an alternative that might help.
Set up a local source control system, such as Subversion. Then get the Subversion plugin for Eclipse. Use Team | Share Project to place the source code into Subversion. After you make changes, use Team | Create Patch to create a patch file and send that to your friend. Your friend can then apply the patch to his source. Of course, your fiend should also be using Subversion and follow these same steps. In addition, remember to commit your changes to Subversion both when you send a patch to him and after you apply a patch he sends to you.
This is not ideal, but should be workable is you are diligent in sharing patches. But just to verify that your code is in synch one of you should periodically send the full source to the other who would then do a diff to verify that things are in synch.
I am currently using a variation of this method to maintain source code with one of my colleagues.