Right. However, we have optimized application deployment and storage based on the assumption that many common java libraries will be shared by a large number of applications. This gives many of the advantages that you are looking for (e.g. you won't upload foo-1.2.3.jar if at least one other application has already used an identical file) without any of the disadvantages Peter mentioned.
On Tue, Dec 1, 2009 at 4:13 PM, Peter Liu <[email protected]> wrote: > My guess is that the jars you uploaded are the ones that will be used. > If the environment just use google's jar we have no control on what > version to use. Say if google release a new release and triggers a bug > in our code, we better off sticking with the old jars instead. > > On Dec 1, 1:55 pm, Yiming Li <[email protected]> wrote: > > Hi All, > > I was just wondering, when we upload the app to Google, what > > is the point of uploading the jar files under war/lib directory, I > > think Google could provide these jars on their side. > > I tried to remove the jars, but I get an error when uploading the > app. > > > > Yiming > > -- > > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
