Actually, if your project was under versioning control, all developers would be using the same jars. :)
You can avoid this by configuring Eclipse libraries, and then each developer could configure its own, and export it with an Ant build. Best Regards, -- Guilherme Petterle Silveira Mussi Conrad Caine Media Applications GmbH Mobile: +55 53 91257012 Office: +55 53 30275721 "Any fool can know. The point is to understand." - Albert Einstein On Mon, Apr 26, 2010 at 8:39 AM, jbdhl <[email protected]> wrote: > In GWT projects, .jar files should eventually end up in war/WEB-INF/ > lib/, but this lib/ dir is kind of dynamic as Eclipse automatically > copies relevant GWT and GAE jars to it. Therefore, if lib/ was under > version control, its contents would likely be re-committed each time a > new developer commits -- depending on which local jar versions he > uses. I would therfore rather prefer to store my external jar files > (such as "objectify.jar") in another directory, say > "toBeCopiedToLib/", and have this dir, with very limited and static > content, under version control. Then, upon each build toBeCopiedToLib/ > *.jar should be copied to lib/. > > How can I do this? (I use Eclipse with the Google plugin - not an ant > build file from a terminal) > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
