Right, when you uncheck the GWT/App Engine checkbox it expands the SDK libraries into individual build path entries. What I'm still not seeing is why that is desirable. Why wouldn't you always leave the project in the same state is if the SDK had never been a part of it? I'm still not seeing how the SDK expansion feature helps, regardless of the origin of the project.
You're removing a resource from the project, just like removing a reference to another project or a user library. If it turns out that the resource is still required, something breaks. That's "natural" and exactly what I would expect. This "oh, maybe you didn't mean to remove those libraries, so I'll just leave them here on the shelf for you" confuses me, and I'm trying to understand the use case that drives it, since the feature also inconveniences other use cases. I don't mean to belabor the point, but having to clean up after tools is a pet peeve of mine. 2009/5/19 Miguel Méndez <[email protected]>: > In that case, it leaves the project the way that it found it. This > expansion only takes place when you uncheck the Use GWT/App Engine checkbox > in the project properties. > > On Tue, May 19, 2009 at 1:13 PM, Isaac Truett <[email protected]> wrote: >> >> That is a viable work around. Thanks. >> >> Perhaps I'm being dense on this, but I don't see how the feature >> supports your script-created project use case. How does the SDK >> expansion help you use the Eclipse plugin with a project that was >> created without the plugin? >> >> >> 2009/5/19 Miguel Méndez <[email protected]>: >> > The case that we wanted to support was one where you use the >> > webAppCreator >> > script from the command line and then you want to try the plugin against >> > it. >> > If you don't want the expansion to take place, remove the GWT/App Engine >> > SDK >> > through the build classpath and then disable GWT/App Engine. That will >> > prevent the expansion. >> > >> > On Tue, May 19, 2009 at 12:42 PM, Isaac Truett <[email protected]> >> > wrote: >> >> >> >> >> Uh-huh ... I thought that if I disabled the GWT and/or App Engine >> >> >> SDK, >> >> >> all >> >> >> related jars should be removed. >> >> >> >> >> >> The project structure should be restored before the GWT and/or App >> >> >> Engine >> >> >> SDK is enabled :-) >> >> > >> >> > We don't because your code could be referring to them even though it >> >> > is >> >> > not >> >> > a GWT/App Engine project according to the plugin. We just replace >> >> > the >> >> > container with the jars that it expands to, remove the necessary >> >> > nature >> >> > and >> >> > builders. You can always go back and remove all of the jars if you >> >> > really >> >> > don't need them. >> >> > >> >> >> >> I certainly understand your reasoning, but that's not normal Eclipse >> >> behavior in my experience. If you remove the JDK, for example, it >> >> doesn't add rt.jar to your classpath just in case you were referencing >> >> it. I would expect adding GWT/App Engine to your project and then >> >> removing it again to leave the project as it started. >> >> >> >> >> >> 2009/5/19 Miguel Méndez <[email protected]>: >> >> > On Tue, May 19, 2009 at 12:23 PM, hezjing <[email protected]> wrote: >> >> >> >> >> >> Hi >> >> >> Uh-huh ... I thought that if I disabled the GWT and/or App Engine >> >> >> SDK, >> >> >> all >> >> >> related jars should be removed. >> >> >> >> >> >> The project structure should be restored before the GWT and/or App >> >> >> Engine >> >> >> SDK is enabled :-) >> >> > >> >> > We don't because your code could be referring to them even though it >> >> > is >> >> > not >> >> > a GWT/App Engine project according to the plugin. We just replace >> >> > the >> >> > container with the jars that it expands to, remove the necessary >> >> > nature >> >> > and >> >> > builders. You can always go back and remove all of the jars if you >> >> > really >> >> > don't need them. >> >> > >> >> >> >> >> >> BTW, why the JARs in step 3 (when the project is imported) and step >> >> >> 4 >> >> >> (when the App Engine SDK is disabled) are not displayed under the >> >> >> Referenced >> >> >> Libraries? For example: >> >> > >> >> > They should if you refresh the project. The project view doesn't >> >> > always >> >> > update when container changes are made. >> >> > >> >> >> >> >> >> GwtRpcSpringExample >> >> >> + src >> >> >> + App Engine SDK [App Engine - 1.2.1] >> >> >> + GWT SDK [GWT - 1.6.4] >> >> >> + JRE System Library [jre1.5.0_18] >> >> >> + Referenced Libraries >> >> >> + antr-2.7.6.jar >> >> >> + commons-logging.jar >> >> >> + gwt-servlet.jar >> >> >> + spring-aop.jar >> >> >> + spring-beans.jar >> >> >> + spring-context.jar >> >> >> >> >> >> 2009/5/20 Miguel Méndez <[email protected]> >> >> >>> >> >> >>> The GWT and App Engine SDKs are containers that resolve into >> >> >>> several >> >> >>> jars. When you remove a GWT and/or App Engine SDK, the containers >> >> >>> are >> >> >>> replaced with the jars that they resolve to. Hence you end up with >> >> >>> more >> >> >>> jars. >> >> >>> >> >> >>> On Tue, May 19, 2009 at 10:55 AM, hezjing <[email protected]> >> >> >>> wrote: >> >> >>>> >> >> >>>> Hi >> >> >>>> I noticed the following behaviour when disabled Google App Engine >> >> >>>> SDK >> >> >>>> in >> >> >>>> Eclipse. >> >> >>>> Here are the steps I performed: >> >> >>>> 1) >> >> >>>> >> >> >>>> >> >> >>>> Download http://gwtrpc-spring.googlecode.com/files/GwtRpcSpringExample.zip. >> >> >>>> 2) Extract GwtRpcSpringExample.zip to C:\GwtRpcSpringExample. >> >> >>>> 3) Import the GwtRpcSpringExample project into Eclipse 3.4.2 >> >> >>>> File->Import...->Existing Projects into Workspace, Select root >> >> >>>> directory: C:\GwtRpcSpringExample >> >> >>>> The following is GwtRpcSpringExample project structure shown in >> >> >>>> Eclipse: >> >> >>>> GwtRpcSpringExample >> >> >>>> + src >> >> >>>> + App Engine SDK [App Engine - 1.2.1] >> >> >>>> + GWT SDK [GWT - 1.6.4] >> >> >>>> + JRE System Library [jre1.5.0_18] >> >> >>>> + antr-2.7.6.jar >> >> >>>> + commons-logging.jar >> >> >>>> + gwt-servlet.jar >> >> >>>> + spring-aop.jar >> >> >>>> + spring-beans.jar >> >> >>>> + spring-context.jar >> >> >>>> + spring-core.jar >> >> >>>> + spring-web.jar >> >> >>>> + gwtrpc-spring-1.0.jar >> >> >>>> + war >> >> >>>> 4) Disable the Google App Engine SDK >> >> >>>> GwtRpcSpringExample->Google->App Engine Settings..., Uncheck use >> >> >>>> Google >> >> >>>> App Engine >> >> >>>> The following is GwtRpcSpringExample project structure shown in >> >> >>>> Eclipse: >> >> >>>> GwtRpcSpringExample >> >> >>>> + src >> >> >>>> + appengine-local-runtime-shared.jar >> >> >>>> + geronimo-el_1.0_spec-1.0.1.jar >> >> >>>> + geronimo-jsp_2.1_spec-1.0.1.jar >> >> >>>> + geronimo-servlet_2.5_spec-1.2.jar >> >> >>>> + repackaged-appengine-ant-1.6.5.jar >> >> >>>> + repackaged-appengine-ant-launcher-1.6.5.jar >> >> >>>> ... >> >> >>>> + geronimo-jpa_3.0_spec-1.1.1.jar >> >> >>>> + geronimo-jta_1.1_spec-1.1.1.jar >> >> >>>> + jdo2-api-2.3-SNAPSHOT.jar >> >> >>>> + appengine-tools.api.jar >> >> >>>> + GWT SDK [GWT - 1.6.4] >> >> >>>> + JRE System Library [jre1.5.0_18] >> >> >>>> + antr-2.7.6.jar >> >> >>>> + commons-logging.jar >> >> >>>> + gwt-servlet.jar >> >> >>>> + spring-aop.jar >> >> >>>> + spring-beans.jar >> >> >>>> + spring-context.jar >> >> >>>> + spring-core.jar >> >> >>>> + spring-web.jar >> >> >>>> + gwtrpc-spring-1.0.jar >> >> >>>> + war >> >> >>>> Please note that there are many other JARs added in between src >> >> >>>> and GWT >> >> >>>> SDK, e.g. geronimo*.jar, repackaged-appengine*.jar >> >> >>>> Is this normal? >> >> >>>> >> >> >>>> -- >> >> >>>> >> >> >>>> Hez >> >> >>>> >> >> >>>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> -- >> >> >>> Miguel >> >> >>> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Hez >> >> >> >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Miguel >> >> > >> >> > > >> >> > >> >> >> >> >> > >> > >> > >> > -- >> > Miguel >> > >> > > >> > >> >> > > > > -- > Miguel > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
