Skip to Content

Changes for page Debugging WOLips

Last modified by Pascal Robert on 2012/02/11 05:22
From version 34.1
edited by mark_ritchie
on 2010/02/17 18:07
Change comment: Updated with details on fixing WebObjects library locations.
To version 53.1
edited by mark_ritchie
on 2010/02/17 13:52
Change comment: dratted extra space

Summary

Details

Page properties
Content
... ... @@ -16,15 +16,11 @@
16 16  
17 17  {{panel title="Snow Leopard Update" bgColor="#FFFFCE"}}
18 18  
19 -I gave this a go on Snow Leopard and it worked ok however there were a few problems which I've detailed near the end of this document.
19 +I gave this a go on Snow Leopard and it worked fine with one little detail which I've noted at the end of this page.
20 20  Here's the setup I was using:
21 -- Mac OS X 10.6.2
22 -- WebObjects 5.4.3
21 +- Mac OS X 10.6.1
23 23  - Java 1.6.0_15
24 -- Eclipse 3.4.2 Build id: M20090211-1700 (eclipse-SDK-3.4.2-macosx-carbon.tar.gz)
25 -- woproject svn repository version 6031
26 -- Wonder svn repository version 10655
27 -YMMV!
23 +- Eclipse 3.4.2 (eclipse-SDK-3.4.2-macosx-carbon.tar.gz)
28 28  
29 29  {{/panel}}
30 30  
... ... @@ -120,20 +120,8 @@
120 120  * org.objectstyle.wolips.groovy.ui
121 121  * org.objectstyle.wolips.jprofiler.launching
122 122  
123 -=== Error message: Libraries not found for JavaEOAccess and other WebObjects libraries ===
119 +== The run configuration setup ==
124 124  
125 -A couple projects have been committed to the repository with references to WebObjects libraries in /Library/WebObjects/lib. You'll need to update these to the correct location on your machine. If you've done nothing special to your WebObjects environment then this should be something like: /System/Library/Frameworks
126 -If you've done something else then you'll need to change the library locations (or perhaps update your WOLips properties file.)
127 -
128 -=== Error message: Cannot find artifact for parent POM... ===
129 -
130 -When building woenvironment, you might hit this error:
131 -Cannot find artifact for parent POM: org.objectstyle.woproject:woproject-all-parent::2.1 for project org.objectstyle.woproject.ant:woenvironment:jar:2.1-SNAPSHOT at /Users/...
132 -
133 -The simple solution is delete the pom.xml file. Full details are here: [[http://wiki.objectstyle.org/confluence/display/WOL/mail/6259075]]
134 -
135 -== The configuration setup ==
136 -
137 137  At this point, you should have a long list of packages which should all be compiling.
138 138  If that's not the case, please document additional steps here, making special note of your setup.
139 139  
... ... @@ -161,7 +161,7 @@
161 161  
162 162  == Snow Leopard Update ==
163 163  
164 -I was running the carbon version of Eclipse 3.4.2 Build id: M20090211-1700 on Snow Leopard 10.6.2
148 +I was running the carbon version of Eclipse 3.4.2 on Snow Leopard.
165 165  Up to this point, I was following the instructions above however when I tried to launch Eclipse, I got this error:
166 166  
167 167  {{code value="java"}}
... ... @@ -173,14 +173,11 @@
173 173  
174 174  {{/code}}
175 175  
176 -This is a known problem and is documented here: [[http://www.eclipse.org/swt/faq.php#cocoa32launch]]
160 +This is a known problem and is documented <a href="http:~/~/www.eclipse.org/swt/faq.php#cocoa32launch">here</a>
177 177  The fix is to add the --d32 parameter to the launch arguments.--
178 178  
179 179  Original: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl}
180 180  Updated: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl} --d32--
181 181  
182 -A second problem which I encountered was running out of memory while running test version of Eclipse!
183 -I had to add the VM argument "-Xmx2G" and then 'Run' as opposed to 'Debug' the app. For the most part, that worked.
184 -
185 185  My final setup looked like this:
186 -[[image:32Bit_jvm_2GB_mem.png]]
167 +[[image:32Bit_jvm_arguments.png]]