Skip to Content

Changes for page Debugging WOLips

Last modified by Pascal Robert on 2012/02/11 05:22
From 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!
To version 56.1
edited by mark_ritchie
on 2010/02/17 16:21
Change comment: fixed link

Summary

Details

Page properties
Content
... ... @@ -64,12 +64,9 @@
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.**
67 67  
68 -*
69 -**
70 -*** EntityModler, eomodeldoc and org.objectstyle.wolips.eomodeler.factories
71 - are special projects which require special setup and caffination before touching.
72 -
73 73  The import of wolips should look like this:
74 74  [[image:wolipsImport.png]]
75 75  
... ... @@ -119,6 +119,13 @@
119 119  * org.objectstyle.wolips.groovy.ui
120 120  * org.objectstyle.wolips.jprofiler.launching
121 121  
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 +
122 122  == The run configuration setup ==
123 123  
124 124  At this point, you should have a long list of packages which should all be compiling.
... ... @@ -160,7 +160,7 @@
160 160  
161 161  {{/code}}
162 162  
163 -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]]
164 164  The fix is to add the --d32 parameter to the launch arguments.--
165 165  
166 166  Original: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl}