Skip to Content

Changes for page Debugging WOLips

Last modified by Pascal Robert on 2012/02/11 05:22
From version 56.1
edited by mark_ritchie
on 2010/02/17 16:21
Change comment: fixed link
To version 60.1
edited by mark_ritchie
on 2010/02/17 13:50
Change comment: Those three *'s are supposed to be *'s not a bullet list!

Summary

Details

Page properties
Content
... ... @@ -64,9 +64,12 @@
64 64  === Import wolips projects into your workspace ===
65 65  
66 66  Repeat the steps above and import all the wolips projects except for 3!
67 -**EntityModler, eomodeldoc and org.objectstyle.wolips.eomodeler.factories
68 -are special projects which require special setup and caffination before touching.**
69 69  
68 +*
69 +**
70 +*** EntityModler, eomodeldoc and org.objectstyle.wolips.eomodeler.factories
71 + are special projects which require special setup and caffination before touching.
72 +
70 70  The import of wolips should look like this:
71 71  [[image:wolipsImport.png]]
72 72  
... ... @@ -116,13 +116,6 @@
116 116  * org.objectstyle.wolips.groovy.ui
117 117  * org.objectstyle.wolips.jprofiler.launching
118 118  
119 -=== Error message: Cannot find artifact for parent POM... ===
120 -
121 -When building woenvironment, you might hit this error:
122 -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/...
123 -
124 -The simple solution is delete the pom.xml file. Full details are here: [[http://wiki.objectstyle.org/confluence/display/WOL/mail/6259075]]
125 -
126 126  == The run configuration setup ==
127 127  
128 128  At this point, you should have a long list of packages which should all be compiling.
... ... @@ -164,7 +164,7 @@
164 164  
165 165  {{/code}}
166 166  
167 -This is a known problem and is documented here: [[http://www.eclipse.org/swt/faq.php#cocoa32launch]]
163 +This is a known problem and is documented <a href="http:~/~/www.eclipse.org/swt/faq.php#cocoa32launch">here</a>
168 168  The fix is to add the --d32 parameter to the launch arguments.--
169 169  
170 170  Original: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl}