Skip to Content

Changes for page Getting started

Last modified by Maik Musall on 2021/06/16 09:17
From version 19.1
edited by Lachlan Deck
on 2009/09/01 15:34
Change comment: There is no comment for this version
To version 20.1
edited by Lachlan Deck
on 2009/09/01 15:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  == Introduction ==
6 6  
7 -This guide is aimed at those who'd like to set up a local wolips development environment utilising maven and scm (git, svn). At least, these are the steps that I (ldeck) travel through.
7 +This guide is aimed at those who'd like to set up a local wolips development environment utilising maven and scm (git, svn).
8 8  
9 9  == Install Maven ==
10 10  
... ... @@ -107,10 +107,6 @@
107 107  Fragments selected: all fragments of 'Maven Integration'
108 108  [[image:fragments_wolips.png]]
109 109  
110 -===== Step 7 - Other plugins =====
111 -
112 -Oh, sure I also install jadclipse (http:~/~/jadclipse.sf.net/update) for keeping in touch with things but that's beyond the scope of this guide.
113 -
114 114  == Configuring Eclipse ==
115 115  
116 116  ==== wolips binding validation ====
... ... @@ -121,12 +121,6 @@
121 121  
122 122  [[image:wolips_nospaces.png]]
123 123  
124 -==== wolips launching ====
125 -
126 -As of this writing, wolips has forgotten to set the key "-WOHost" with value "localhost". Add it.
127 -I also untick a few things that don't need to be specifically ticked so that your project's properties are used (as you're mimicking the deployment env locally)
128 -[[image:wolips_launching.png]]
129 -
130 130  ==== Set the default jvm ====
131 131  
132 132  [[image:prefs_jvm.png]]
... ... @@ -137,7 +137,7 @@
137 137  
138 138  ==== Java Templates prefs ====
139 139  
140 -[[image:prefs_java_templates.png]]
130 +[[image:prefs_java_teplates.png]]
141 141  
142 142  ==== Run / Debug prefs ====
143 143  
... ... @@ -157,49 +157,3 @@
157 157  ==== UTF-8 Thanks ====
158 158  
159 159  [[image:prefs_utf8.png]]
160 -
161 -== Creating a project ==
162 -
163 -TODO
164 -
165 -== Launching your project ==
166 -
167 -==== Configure eomodel connection dictionaries, log4j, additional properties ====
168 -
169 -In my application projects I create an additional folder called 'Properties' which contains additional property files for differing launches.
170 -e.g.,
171 -When connecting to a local database I use the local files listed below during launch:
172 -
173 -{{noformat}}
174 -
175 -jdbc.local.properties
176 -log4j.local.properties
177 -runtime.local.properties
178 -...
179 -jdbc.test.properties
180 -log4j.test.properties
181 -runtime.test.properties
182 -
183 -{{/noformat}}
184 -
185 -To achieve this switching easily I define in the launch configuration for the application the following two additional properties (from those defined globally in WOLips prefs)
186 -
187 -* key: --runtime.config.dir value:"../../Properties"--
188 -* key: --runtime.config.name value:".local"--
189 -
190 -And in my application's Properties file I have the following properties declared
191 -
192 -{{noformat}}
193 -
194 -runtime.config.dir=Properties
195 -runtime.config.name=
196 -
197 -er.extensions.ERXProperties.OptionalConfigurationFiles=(\
198 -@@runtime.config.dir@@/log4j@@runtime.config.name@@.properties,\
199 -@@runtime.config.dir@@/jdbc@@runtime.config.name@@.properties,\
200 -@@runtime.config.dir@@/runtime@@runtime.config.name@@.properties\
201 -)
202 -
203 -{{/noformat}}
204 -
205 -Naturally, within the jdbc property files are the relevant project wonder properties for configuring the eomodels connection dictionaries, withing the lo4j files are the relevant config for log4j, and runtime properties is available for any special configuration for that particular environment.