Re: Eclipse 3.4.1 and WOLIPS 3.4.5XXX
This evening, I needed to use this fix when I used Jeremy Matthews http://sisuworks.com/files/Eclipse+WOLips.zip Jim Oser On Feb 19, 2009, at 2:17 PM, Chuck Hill wrote: On Feb 19, 2009, at 1:54 PM, Kervella Thierry-Alain wrote: Hi John and thanks for your reply ! The error is the following : Unbound classpath container: 'JavaEOAccess WebObjects Framework' in project 'HelloWord' HelloWord Build path Build Path Problem OK, that is what we needed to know. You are missing this file: saskatoon-3:~ chuck$ cat ~/Library/Application\ Support/WOLips/ wolips.properties #Fri Oct 17 14:08:02 PDT 2008 wo.system.root=/System wo.user.frameworks=/Users/chuck/Library/Frameworks wo.system.frameworks=/System/Library/Frameworks wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/ wotaskd.woa/WOBootstrap.jar wo.network.frameworks=/Network/Library/Frameworks wo.api.root=/Developer/ADC%20Reference%20Library/documentation/ WebObjects/Reference/API/ wo.network.root=/Network wo.extensions=/Library/WebObjects/Extensions wo.user.root=/Users/chuck wo.local.frameworks=/Library/Frameworks wo.apps.root=/Library/WebObjects/Applications wo.local.root=/ I'll suggest that you remove the WOLips you have installed, install the Nightly version and try again. That version should automatically create this file. If you don't want to do that, just create this file in a text editor using the contents above and edit to match your machine. Chuck The same error is applied to JavaEOControl, JavaFoundation, JavaJDBCAdaptor, JavaWebObjects, etc. In Eclipse Pref, in Java Build path variables, JRE_Lib and other are deprecated. in Java preferences, I've positionned JAVA 5 as main java machine ! What else can be done !! Thanks in advance. Thierry-Alain Le 19 févr. 09 à 22:32, John Huss a écrit : What are the errors? On Thu, Feb 19, 2009 at 3:24 PM, Kervella Thierry-Alain takerve...@me.com wrote: Hi, i'm trying to learn WOLIPS. i've installed Eclipse on OSX (ver 3.4.1) plus WOLIPS (vers 3.4.5XXX) and test the classical HelloWord program. Helas, when I compile the program, I've build path errors but don't know where to find solution to solve it. Java JVM is 1.5 by default- Can someone help me. Thanks in advance ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com This email sent to johnth...@gmail.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net This email sent to ch...@global-village.net -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/oserj%40oserconsulting.com This email sent to os...@oserconsulting.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Eclipse 3.4.1 and WOLIPS 3.4.5XXX
Hi Chuck, thanks a lot - Your method has corrected the problem Great ! Le 19 févr. 09 à 23:17, Chuck Hill a écrit : On Feb 19, 2009, at 1:54 PM, Kervella Thierry-Alain wrote: Hi John and thanks for your reply ! The error is the following : Unbound classpath container: 'JavaEOAccess WebObjects Framework' in project 'HelloWord' HelloWord Build path Build Path Problem OK, that is what we needed to know. You are missing this file: saskatoon-3:~ chuck$ cat ~/Library/Application\ Support/WOLips/ wolips.properties #Fri Oct 17 14:08:02 PDT 2008 wo.system.root=/System wo.user.frameworks=/Users/chuck/Library/Frameworks wo.system.frameworks=/System/Library/Frameworks wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/ wotaskd.woa/WOBootstrap.jar wo.network.frameworks=/Network/Library/Frameworks wo.api.root=/Developer/ADC%20Reference%20Library/documentation/ WebObjects/Reference/API/ wo.network.root=/Network wo.extensions=/Library/WebObjects/Extensions wo.user.root=/Users/chuck wo.local.frameworks=/Library/Frameworks wo.apps.root=/Library/WebObjects/Applications wo.local.root=/ I'll suggest that you remove the WOLips you have installed, install the Nightly version and try again. That version should automatically create this file. If you don't want to do that, just create this file in a text editor using the contents above and edit to match your machine. Chuck The same error is applied to JavaEOControl, JavaFoundation, JavaJDBCAdaptor, JavaWebObjects, etc. In Eclipse Pref, in Java Build path variables, JRE_Lib and other are deprecated. in Java preferences, I've positionned JAVA 5 as main java machine ! What else can be done !! Thanks in advance. Thierry-Alain Le 19 févr. 09 à 22:32, John Huss a écrit : What are the errors? On Thu, Feb 19, 2009 at 3:24 PM, Kervella Thierry-Alain takerve...@me.com wrote: Hi, i'm trying to learn WOLIPS. i've installed Eclipse on OSX (ver 3.4.1) plus WOLIPS (vers 3.4.5XXX) and test the classical HelloWord program. Helas, when I compile the program, I've build path errors but don't know where to find solution to solve it. Java JVM is 1.5 by default- Can someone help me. Thanks in advance ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com This email sent to johnth...@gmail.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net This email sent to ch...@global-village.net -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Eclipse 3.4.1 and WOLIPS 3.4.5XXX
Hi John and thanks for your reply ! The error is the following : Unbound classpath container: 'JavaEOAccess WebObjects Framework' in project 'HelloWord' HelloWord Build path Build Path Problem The same error is applied to JavaEOControl, JavaFoundation, JavaJDBCAdaptor, JavaWebObjects, etc. In Eclipse Pref, in Java Build path variables, JRE_Lib and other are deprecated. in Java preferences, I've positionned JAVA 5 as main java machine ! What else can be done !! Thanks in advance. Thierry-Alain Le 19 févr. 09 à 22:32, John Huss a écrit : What are the errors? On Thu, Feb 19, 2009 at 3:24 PM, Kervella Thierry-Alain takerve...@me.com wrote: Hi, i'm trying to learn WOLIPS. i've installed Eclipse on OSX (ver 3.4.1) plus WOLIPS (vers 3.4.5XXX) and test the classical HelloWord program. Helas, when I compile the program, I've build path errors but don't know where to find solution to solve it. Java JVM is 1.5 by default- Can someone help me. Thanks in advance ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com This email sent to johnth...@gmail.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Eclipse 3.4.1 and WOLIPS 3.4.5XXX
On Feb 19, 2009, at 1:54 PM, Kervella Thierry-Alain wrote: Hi John and thanks for your reply ! The error is the following : Unbound classpath container: 'JavaEOAccess WebObjects Framework' in project 'HelloWord' HelloWord Build path Build Path Problem OK, that is what we needed to know. You are missing this file: saskatoon-3:~ chuck$ cat ~/Library/Application\ Support/WOLips/ wolips.properties #Fri Oct 17 14:08:02 PDT 2008 wo.system.root=/System wo.user.frameworks=/Users/chuck/Library/Frameworks wo.system.frameworks=/System/Library/Frameworks wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/ wotaskd.woa/WOBootstrap.jar wo.network.frameworks=/Network/Library/Frameworks wo.api.root=/Developer/ADC%20Reference%20Library/documentation/ WebObjects/Reference/API/ wo.network.root=/Network wo.extensions=/Library/WebObjects/Extensions wo.user.root=/Users/chuck wo.local.frameworks=/Library/Frameworks wo.apps.root=/Library/WebObjects/Applications wo.local.root=/ I'll suggest that you remove the WOLips you have installed, install the Nightly version and try again. That version should automatically create this file. If you don't want to do that, just create this file in a text editor using the contents above and edit to match your machine. Chuck The same error is applied to JavaEOControl, JavaFoundation, JavaJDBCAdaptor, JavaWebObjects, etc. In Eclipse Pref, in Java Build path variables, JRE_Lib and other are deprecated. in Java preferences, I've positionned JAVA 5 as main java machine ! What else can be done !! Thanks in advance. Thierry-Alain Le 19 févr. 09 à 22:32, John Huss a écrit : What are the errors? On Thu, Feb 19, 2009 at 3:24 PM, Kervella Thierry-Alain takerve...@me.com wrote: Hi, i'm trying to learn WOLIPS. i've installed Eclipse on OSX (ver 3.4.1) plus WOLIPS (vers 3.4.5XXX) and test the classical HelloWord program. Helas, when I compile the program, I've build path errors but don't know where to find solution to solve it. Java JVM is 1.5 by default- Can someone help me. Thanks in advance ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/johnthuss%40gmail.com This email sent to johnth...@gmail.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net This email sent to ch...@global-village.net -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Eclipse 3.4.1
In the interests of brevity... [property] Loading /Users/james/Documents/workspace/PWDA/Sources/ build.properties Something in the build.xml is making it think that the project root is /Users/james/Documents/workspace/PWDA/Sources' instead of /Users/james/Documents/workspace/PWDA I think that all of your other problems stem from that. Look at the top of the build.xml: project name=PWDA default=build basedir=. does basedir say Sources there? Chuck On Oct 29, 2008, at 12:56 PM, james o'loughlin wrote: On Oct 28, 2008, at 7:45 PM, Chuck Hill wrote: On Oct 28, 2008, at 3:48 PM, james o'loughlin wrote: On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote: Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined where is this defined? i don't see project.name and project.name.lowercase in the build.properties file... maybe this is my problem? I don't think it is the problem below, but it will be a problem eventually. If you create a new project after upgrading to hotness, you can look at its build.properties to see what is used. actually found this in the build.xml file and not build.properties. - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building new Hotness... check :) - Download and install latest Wonder check - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects check - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn apps build. If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran thank you so much for the checklist kieran! unfortunately, i'm still running into an issue on my ant build -- Buildfile: /Users/james/Documents/workspace/PWDA/build.xml init.properties: init.build: compile: BUILD FAILED /Users/james/Documents/workspace/PWDA/build.xml:207: Failed to process eclipse frameworks. I wonder if you really have updated to new hotness. Or if that project's .classpath has been updated to the hotness form. Maybe try it with ant -verbose as well and see if anything looks suspicious. -verbose, bingo! i get the following error when using -verbose: BUILD FAILED /Users/james/Documents/workspace/PWDA/build.xml:207: srcdir /Users/ james/Documents/workspace/PWDA/Sources/Sources does not exist not sure why it's trying to build with /Sources/Sources? shouldn't my build path be: /Users/james/Documents/workspace/PWDA/Sources --- Apache Ant version 1.7.0 compiled on December 13 2006 Buildfile: /Users/james/Documents/workspace/PWDA/build.xml parsing buildfile /Users/james/Documents/workspace/PWDA/build.xml with URI = file:/Users/james/Documents/workspace/PWDA/build.xml Project base dir set to: /Users/james/Documents/workspace/PWDA/Sources Build sequence for target(s) `build' is [init.properties, init.build, compile, build.woapp, javaclient, ssdd, war, split, package, build] Complete build sequence is [init.properties, init.build, compile, build.woapp, javaclient, ssdd, war, split, package, build, init.install, install, clean, ] init.properties: [antlib:org.apache.tools.ant] Could not load definitions from resource org/apache/tools/ant/antlib.xml. It could not be found. [property] Loading /Users/james/Documents/workspace/PWDA/Sources/ build.properties [property] Unable to find property file: /Users/james/Documents/ workspace/PWDA/Sources/build.properties [property] Loading /Users/james/Library/Application Support/WOLips/ wolips.properties Property project.name has not been set Property project.name.lowercase has not been set init.build: compile: [mkdir] Skipping /Users/james/Documents/workspace/PWDA/Sources/ bin because it already exists. BUILD FAILED /Users/james/Documents/workspace/PWDA/build.xml:207: srcdir /Users/ james/Documents/workspace
Re: Eclipse 3.4.1
On Oct 29, 2008, at 2:24 PM, james o'loughlin wrote: On Oct 29, 2008, at 4:13 PM, Chuck Hill wrote: In the interests of brevity... [property] Loading /Users/james/Documents/workspace/PWDA/Sources/ build.properties Something in the build.xml is making it think that the project root is /Users/james/Documents/workspace/PWDA/Sources' instead of /Users/james/Documents/workspace/PWDA I think that all of your other problems stem from that. Look at the top of the build.xml: project name=PWDA default=build basedir=. does basedir say Sources there? Chuck i don't see an extra Sources in my build.xml. not sure why it would be picking this up. project name=PWDA default=build basedir=. target name=build depends=init.build,build.woapp,javaclient,ssdd,war,split,package / target name=install depends =init.install,build.woapp,javaclient,ssdd,war,split,package / target name=clean depends=init.properties delete dir=bin / delete dir=dist / /target What is in /Users/james/Documents/workspace/PWDA/build.properties? where else would i define the project root? here's my project Properties: Picture 13.png my source folder was always PWDA/Sources, should i change it to just PWDA for new hotness? No! Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
On Oct 29, 2008, at 5:30 PM, Chuck Hill wrote: On Oct 29, 2008, at 2:24 PM, james o'loughlin wrote: On Oct 29, 2008, at 4:13 PM, Chuck Hill wrote: In the interests of brevity... [property] Loading /Users/james/Documents/workspace/PWDA/Sources/ build.properties Something in the build.xml is making it think that the project root is /Users/james/Documents/workspace/PWDA/Sources' instead of /Users/james/Documents/workspace/PWDA I think that all of your other problems stem from that. Look at the top of the build.xml: project name=PWDA default=build basedir=. does basedir say Sources there? Chuck i don't see an extra Sources in my build.xml. not sure why it would be picking this up. project name=PWDA default=build basedir=. target name=build depends=init.build,build.woapp,javaclient,ssdd,war,split,package / target name=install depends =init.install,build.woapp,javaclient,ssdd,war,split,package / target name=clean depends=init.properties delete dir=bin / delete dir=dist / /target What is in /Users/james/Documents/workspace/PWDA/build.properties? here's my build.properties file: #Wed Oct 29 15:42:49 EDT 2008 webXML_CustomContent= project.name=PWDA webXML=false embed.System=true eoAdaptorClassName= principalClass=Application classes.dir=bin embed.Local=true project.name=PWDA project.name.lowercase=pwda customInfoPListContent= project.type=application thanks! ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
On Oct 29, 2008, at 3:35 PM, james o'loughlin wrote: On Oct 29, 2008, at 5:30 PM, Chuck Hill wrote: On Oct 29, 2008, at 2:24 PM, james o'loughlin wrote: On Oct 29, 2008, at 4:13 PM, Chuck Hill wrote: In the interests of brevity... [property] Loading /Users/james/Documents/workspace/PWDA/Sources/ build.properties Something in the build.xml is making it think that the project root is /Users/james/Documents/workspace/PWDA/Sources' instead of /Users/james/Documents/workspace/PWDA I think that all of your other problems stem from that. Look at the top of the build.xml: project name=PWDA default=build basedir=. does basedir say Sources there? Chuck i don't see an extra Sources in my build.xml. not sure why it would be picking this up. project name=PWDA default=build basedir=. target name=build depends =init.build,build.woapp,javaclient,ssdd,war,split,package / target name=install depends =init.install,build.woapp,javaclient,ssdd,war,split,package / target name=clean depends=init.properties delete dir=bin / delete dir=dist / /target What is in /Users/james/Documents/workspace/PWDA/build.properties? here's my build.properties file: #Wed Oct 29 15:42:49 EDT 2008 webXML_CustomContent= project.name=PWDA webXML=false embed.System=true eoAdaptorClassName= principalClass=Application classes.dir=bin embed.Local=true project.name=PWDA project.name.lowercase=pwda customInfoPListContent= project.type=application That looks all OK... Where is your build.xml file? Is it in /Users/james/Documents/ workspace/PWDA or in /Users/james/Documents/workspace/PWDA/Sources? It should be in the former. Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
On Oct 28, 2008, at 3:48 PM, james o'loughlin wrote: On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote: Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined where is this defined? i don't see project.name and project.name.lowercase in the build.properties file... maybe this is my problem? I don't think it is the problem below, but it will be a problem eventually. If you create a new project after upgrading to hotness, you can look at its build.properties to see what is used. - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building new Hotness... check :) - Download and install latest Wonder check - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects check - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn apps build. If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran thank you so much for the checklist kieran! unfortunately, i'm still running into an issue on my ant build -- Buildfile: /Users/james/Documents/workspace/PWDA/build.xml init.properties: init.build: compile: BUILD FAILED /Users/james/Documents/workspace/PWDA/build.xml:207: Failed to process eclipse frameworks. I wonder if you really have updated to new hotness. Or if that project's .classpath has been updated to the hotness form. Maybe try it with ant -verbose as well and see if anything looks suspicious. Total time: 1 second -- build.xml line 207: wocompile srcdir=Sources destdir=bin Can you post the whole wocompile clause? not sure why my build.xml is trying to use eclipse frameworks?! That is what new hotness does. on a side note, where is this fancy, Add Library window located? http://2.bp.blogspot.com/_gRYgZfzU1BE/SL9erDHwi9I/AJo/gUxbOge02BM/s1600-h/Picture+4.png Project - Properties - Java Build Path ... after you update to New Hotness. Chuck On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote: On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder- latest-frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting
Re: Eclipse 3.4.1
On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote: Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building I know this is probably a stupid question with an easy answer, but I will ask it anyway. Is there a way to upgrade Eclipse 3.3 to 3.4.1 within Eclipse or do I have to download a new copy of Eclipse? Thanks, Frank - Download and install latest Wonder - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote: On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder- latest-frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms You make it sound so scary! :-) I take it that it's stable enough though...? The only reason I'm updating is because the new .classpath files were pushed into the repository. I took that as an 'all clear' :-) Everything looks fine so far (knock on wood). Any gotcha's that we should be aware of?? Ramsey ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/frank.cobia%40f2technology.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help
Re: Eclipse 3.4.1
On Oct 28, 2008, at 5:03 PM, Mr. Frank Cobia wrote: On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote: Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building I know this is probably a stupid question with an easy answer, but I will ask it anyway. Is there a way to upgrade Eclipse 3.3 to 3.4.1 within Eclipse or do I have to download a new copy of Eclipse? You have to download a new copy. You can use the new copy with your existing workspace, it will upgrade it. Chuck - Download and install latest Wonder - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote: On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder- latest-frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms You make it sound so scary! :-) I take it that it's stable enough though...? The only reason I'm updating is because the new .classpath files were pushed into the repository. I took that as an 'all clear' :-) Everything looks fine so far (knock on wood). Any gotcha's that we should be aware of?? Ramsey ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/frank.cobia%40f2technology.com This email sent to [EMAIL PROTECTED
Re: Eclipse 3.4.1
Thanks Kieran for these steps... I followed them and converted a small project to the new build hotness. :-) I find the new build hotness more intuitive. :-) I need to re-read the WOLips blog to make sure I understand it better and can get full advantage of it. Thanks, Ricardo Parada On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote: Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building - Download and install latest Wonder - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote: On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder- latest-frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms You make it sound so scary! :-) I take it that it's stable enough though...? The only reason I'm updating is because the new .classpath files were pushed into the repository. I took that as an 'all clear' :-) Everything looks fine so far (knock on wood). Any gotcha's that we should be aware of?? Ramsey ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/rparada %40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects
Re: Eclipse 3.4.1
Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building - Download and install latest Wonder - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote: On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder- latest-frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms You make it sound so scary! :-) I take it that it's stable enough though...? The only reason I'm updating is because the new .classpath files were pushed into the repository. I took that as an 'all clear' :-) Everything looks fine so far (knock on wood). Any gotcha's that we should be aware of?? Ramsey ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
Hmm ... it did not do it for me yesterday (Eclipse 3.4.1, WOLips 5502). I had to go in and change the build order manually pushing ERExtensions to the top to get rid of the NSArray, etc., does not support generics error messages. Nor did it delete the old ant path files in woproject which, IIRC, was a feature of the upgrade. Anyway, no worries, it took only a few minutes to fix all the Build Paths. Thats for the update this is definitely the cleaner way to go and should make it much easier for newbies to link frameworks to projects. Great job. Thanks, Kieran On Oct 14, 2008, at 9:19 AM, Mike Schrag wrote: If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) It should automatically do this ... ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
How about building from the command line? Is a newer version of ant needed? I think I read something about that in one of the emails. I have ant 1.7.0 on my OS X 10.5.5 machine. Is that good? 1.7 is required, yes (which comes standard on Leopard, I believe). 1.6 is on Tiger, so you would need to upgrade your ant (or install an upgraded ant, rather) to build on Tiger. ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) It should automatically do this ... ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
How about building from the command line? Is a newer version of ant needed? I think I read something about that in one of the emails. I have ant 1.7.0 on my OS X 10.5.5 machine. Is that good? On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote: Here is the rough checklist for upgrading ... (in my case I have Wonder source linked into my workspace ... and I use WO 5.3.3) - Every project's build.properties needs to have project.name and project.name.lowercase defined - Check Build Path Order and put ERExtensions at the top of the build order (that is important!) - Do a pre-upgrade commit of everything to svn - Turn off autobuild - Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness) and close Eclipse without building - Download and install latest Wonder - Reopen your 3.4 workspace - Create a new temporary WonderApplication project - Replace your old application build.xml files with new one from temp project - Replace your old application woproject/*.patternsets with new ones from temp project - Create a new temporary WonderFramework project - Replace your old framework build.xml files with new one from temp project - Replace your old framework woproject/*.patternsets with new ones from temp project - Delete your old woproject/ant path whatever files in all projects - Right-click application projects - Properties - Turn on embedding (the more embed checkboxes you turn on, the less fire Future You will be playing with ;-) ) - Clean/Rebuild all - Test app(s) - Commit to svn If you have build issues, open Build Path and check the Order of Frameworks and push ERExtensions to the top (Mike, possibly the automatic upgrade should do this anyway if ERExtensions is in the classpath?) HTH, Kieran On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote: On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder- latest-frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms You make it sound so scary! :-) I take it that it's stable enough though...? The only reason I'm updating is because the new .classpath files were pushed into the repository. I took that as an 'all clear' :-) Everything looks fine so far (knock on wood). Any gotcha's that we should be aware of?? Ramsey ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/rparada %40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http
Eclipse 3.4.1
Hello, I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder-latest- frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( Thanks, Jeff ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
Hi Jeff, I'm doing the same thing now. I had the same problem. I think you're in the wrong view. Go to Window-Show View-Other and pick WO Explorer. Ramsey On Oct 13, 2008, at 11:14 PM, Jeff Schmitz wrote: Hello, I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder-latest- frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( Thanks, Jeff ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/rgurley %40mac.com This email sent to [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
A little more specific info. One of the packages that can't be seen bythe compiler is er.extension.ERXGenericRecord. Looking at the java build path, Libraries, it lists the following as selected (among others): ERExtensions Framework ERJars Framework ERPrototypes Framework. Thanks, Jeff On Oct 13, 2008, at 10:14 PM, Jeff Schmitz wrote: Hello, I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder-latest- frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( Thanks, Jeff ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/jeffandmonica%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
Thanks, I can now see my frameworks listed. It looks like they are all there (see previous e-mail) and yet the compiler doesn't seem to be picking them up. Any ideas? Do I need to regenerate my EOModel classes? Thanks, Jeff On Oct 13, 2008, at 10:43 PM, Ramsey Gurley wrote: Hi Jeff, I'm doing the same thing now. I had the same problem. I think you're in the wrong view. Go to Window-Show View-Other and pick WO Explorer. Ramsey On Oct 13, 2008, at 11:14 PM, Jeff Schmitz wrote: Hello, I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder-latest- frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( Thanks, Jeff ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/rgurley%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder-latest- frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
A little more specific info. One of the packages that can't be seen bythe compiler is er.extension.ERXGenericRecord. If you're using a version of Wonder newer than June, this is the wrong package for ERXGenericRecord. Wonder 5 was refactored into packages (see the June 7th post on the Project Wonder blog -- http://projectwonder.blogspot.com/2008/06/this-week-in-project-wonder.html) . ERXGenericRecord is now er.extensions.eof.ERXGenericRecord. ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
I think I want to go back. Would my time machine backup be the easiest thing to do? On Oct 13, 2008, at 10:58 PM, Mike Schrag wrote: A little more specific info. One of the packages that can't be seen bythe compiler is er.extension.ERXGenericRecord. If you're using a version of Wonder newer than June, this is the wrong package for ERXGenericRecord. Wonder 5 was refactored into packages (see the June 7th post on the Project Wonder blog -- http://projectwonder.blogspot.com/2008/06/this-week-in-project-wonder.html) . ERXGenericRecord is now er.extensions.eof.ERXGenericRecord. ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/jeffandmonica%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote: I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly build and downloaded and installed the lastest Wonder-latest- frameworks-5.4. Now, when I open my workspace I don't see my WOFrameworks folder, and neither does eclipse since nothing in the ERX framework compiles. What can I do to get my frameworks back into my project? I tried looking at the filters, but there are only two listed, *.class and .* Even when I try to open Eclipse 3.3 my frameworks can no longer be seen. Why would upgrading have blasted my project's framework setup? And why was I dumb enough to try this in the first place :-( WOLips 3.4 has an entirely new classpath system. Touching a WOLips 3.3 project with WOLips 3.4 will cause the .classpath file to be upgraded, and it is not backwards compatible. WO Frameworks are no longer handled as a single classpath container, rather each framework is now managed independently as its own classpath container (which more closely matches reality), and they each appear as Libraries in your build path. As far as ERX not compiling, I'm not sure what version of the source you have, but given that the trunk of Wonder has been upgraded to WOLips 3.4, and I check it out all the time, I can assure you that it compiles without any errors under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you will need to change the build path of WOOGNL to remove Sources_53 and add Sources_54, but other than that, things should work fine. That said, nightly is not stable for a reason. If you're using nightly, you should really either be on the wolips mailing list or you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html ), so you know what you're getting yourself into. There are SUBSTANTIAL changes to the way things work in the new WOLips that you need to be aware of. ms You make it sound so scary! :-) I take it that it's stable enough though...? The only reason I'm updating is because the new .classpath files were pushed into the repository. I took that as an 'all clear' :-) Everything looks fine so far (knock on wood). Any gotcha's that we should be aware of?? Ramsey smime.p7s Description: S/MIME cryptographic signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Eclipse 3.4.1
FYI, time machine worked like a charm. Just moved my frameworks dir and my whole workspace back to this morning. Very nice! Jeff On Oct 13, 2008, at 11:00 PM, Jeff Schmitz wrote: I think I want to go back. Would my time machine backup be the easiest thing to do? On Oct 13, 2008, at 10:58 PM, Mike Schrag wrote: A little more specific info. One of the packages that can't be seen bythe compiler is er.extension.ERXGenericRecord. If you're using a version of Wonder newer than June, this is the wrong package for ERXGenericRecord. Wonder 5 was refactored into packages (see the June 7th post on the Project Wonder blog -- http://projectwonder.blogspot.com/2008/06/this-week-in-project-wonder.html) . ERXGenericRecord is now er.extensions.eof.ERXGenericRecord. ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/jeffandmonica%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/jeffandmonica%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
