Changes for page Debugging WOLips

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,9 +7,3 @@
1		-{{note title="Under Construction"}}
2		-
3		-This page is currently under construction by Mark Ritchie!
4		-
5		-{{/note}}
6		-
7	7	= Debugging WOLips as the master does! =
8	8
9	9	These instructions is intended for the developer who wants to compile and run WOLips source for the purpose of debugging or other exploration. Thanks very much to Mike Schrag for the guidance to get this setup and working!
...	...	@@ -40,23 +40,101 @@
40	40	I chose ,,/WOLipsDebugging
41	41	[[image:Workspace.png]],,
42	42
43		-=== Import woenvironment ===
	37	+=== Import woenvironment ===
44	44
	39	+Start off by importing the woenvironment project. From the File menu, select Import
	40	+[[image:ImportMenu.png]]
	41	+Click the disclosure triangle for General and select Existing Projects into Workspace
	42	+[[image:ExistingProject.png]]
	43	+Click Next button.
	44	+Ensure that "Select root directory" is selected and click Browse
	45	+Browse to the folder where you checked out the woproject source code above and select woenvironment.
	46	+[[image:woenvironmentCheckout.png]]
	47	+Eclipse should scan the folder and notice one project in the folder called woenvironment.
	48	+**It's important that you don't have 'Copy the project into your workspace' selected.**
	49	+[[image:woenvironmentProject.png]]
	50	+Click Finish.
	51	+
	52	+Once Eclipse has finished building the project, there should be no errors! If that's not the case, then you need to back up and make sure that you've followed all the steps above.
	53	+
45	45	=== Import wolips projects into your workspace ===
46	46
	56	+Repeat the steps above and import all the wolips projects except for 3!
	57	+**EntityModler, eomodeldoc and org.objectstyle.wolips.eomodeler.factories
	58	+Are special projects which require special setup and caffination before touching.**
	59	+
	60	+The import of wolips should look like this:
	61	+[[image:wolipsImport.png]]
	62	+
	63	+And Eclipse should identify a whole bunch of projects.
	64	+**Make sure that you deselect the 3 special cases noted above**
	65	+The list of projects should look something like this:
	66	+[[image:wolipsProjects.png]]
	67	+
	68	+Click Finish and the projects should all be imported.
	69	+
	70	+{{note}}
	71	+
	72	+When I did this I got the following error message.
	73	+I have no idea what this means...
	74	+!ResourceErrorMessage.png!
	75	+
	76	+{{/note}}
	77	+
	78	+Once Eclipse finishes building the projects there are going to be a whole bunch of build errors. Don't Panic. Most of them will resolve themselves after the next steps.
	79	+
47	47	=== Import wolips plugins ===
48	48
	82	+In the same way as above, import the core plugins from wolips/core/plugins. Something like this:
	83	+[[image:corePluginImport.png]]
	84	+[[image:corePluginProjects.png]]
	85	+
49	49	=== Import 3rd party plugins ===
50	50
	88	+Finally, import the third party plugins from wolips/3rdparty/plugin. Something like this:
	89	+[[image:thridPartyImport.png]]
	90	+[[image:thirdPartyProjects.png]]
	91	+
51	51	=== Close special projects ===
52	52
	94	+In case you missed the notices above, close these projects.
	95	+
53	53	* EntityModeler
54	54	* eomodeldoc
55	55	* org.objectstyle.wolips.eomodeler.factories
	99	+(Note: Working on these projects is beyond the scope of what I needed to do. Sorry.)
56	56
57	57	=== Close projects which require additional resources to compile ===
58	58
	103	+These projects require additional resources to compile. As I didn't need them, I just closed them.
	104	+
	105	+* org.objectstyle.wolips.apple.mavenintegration
59	59	* org.objectstyle.wolips.groovy.ui
60	60	* org.objectstyle.wolips.jprofiler.launching
61	61
62	62	== The run configuration setup ==
	110	+
	111	+At this point, you should have a long list of packages which should all be compiling.
	112	+If that's not the case, please document additional steps here, making special note of your setup.
	113	+
	114	+Getting on with the configuration to be able to test the software which is now compiling.
	115	+From the Run menu, select "Debug Configurations ..."
	116	+[[image:debugConfiguration.png]]
	117	+
	118	+Select "Eclipse Application" from the list on the left
	119	+and then click the "New" button at the top.
	120	+[[image:newLaunchConfiguration.png]]
	121	+This creates a new launch configuration which you can customize as you like.
	122	+By default it's called 'New//configuration'. For this session, I named it DebugEclipse//
	123	+
	124	+My preference is to explicitly set the workspace for testing however I'm sure the default will be fine if you like it.
	125	+I chose: $workspace//loc}/../WOLipsDebuggingWorkspace
	126	+My setup looked something like below however there are lots of configuration options which I didn't need to explore:
	127	+[[image:debugConfigured.png]]//
	128	+
	129	+== Launch the debug version ==
	130	+
	131	+Click the Debug button in the debug configuration window to launch the test version.
	132	+This will be a clean version of Eclipse with the workspace which you set and any other settings.
	133	+By default, all of the plugins are loaded and ready for testing!
	134	+And now, you should be running inside the debug version of Eclipse with all the wolips bits to play with!