Skip to Content

Changes for page Debugging WOLips

Last modified by Pascal Robert on 2012/02/11 05:22
From version 65.1
edited by mark_ritchie
on 2009/09/14 02:05
Change comment: There is no comment for this version
To version 56.1
edited by mark_ritchie
on 2010/02/17 16:21
Change comment: fixed link

Summary

Details

Page properties
Content
... ... @@ -65,7 +65,7 @@
65 65  
66 66  Repeat the steps above and import all the wolips projects except for 3!
67 67  **EntityModler, eomodeldoc and org.objectstyle.wolips.eomodeler.factories
68 -Are special projects which require special setup and caffination before touching.**
68 +are special projects which require special setup and caffination before touching.**
69 69  
70 70  The import of wolips should look like this:
71 71  [[image:wolipsImport.png]]
... ... @@ -116,6 +116,13 @@
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 +
119 119  == The run configuration setup ==
120 120  
121 121  At this point, you should have a long list of packages which should all be compiling.
... ... @@ -157,7 +157,7 @@
157 157  
158 158  {{/code}}
159 159  
160 -This is a known problem and is documented <a href="http:~/~/www.eclipse.org/swt/faq.php#cocoa32launch">here</a>
167 +This is a known problem and is documented here: [[http://www.eclipse.org/swt/faq.php#cocoa32launch]]
161 161  The fix is to add the --d32 parameter to the launch arguments.--
162 162  
163 163  Original: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl}