Hi Jeff,
On 30 Jan 2018, at 14:05, Jeff Schmitz wrote:
> I recently updated to Eclipse Oxygen and somewhere in the process my
> EOGenerator behavior has been changed.
As an aside to Johann’s explanation, we got into the practice some time ago of
including EOGenerator templates in every projec
Hi Jeff,
the (very) old EO templates used to use log4j for logging but this was replaced
by slf4j in the current ones some time ago. Perhaps you have a lib problem
there? Passing a null value to e.g. the debug method of slf4j should be no
problem as it converts that to the string „null“ before
Hello List,
I recently updated to Eclipse Oxygen and somewhere in the process my
EOGenerator behavior has been changed. Specifically, where it used to generate
“set” functions like this:
public void setMiscState1(Boolean value) {
if (_Entry.LOG.isDebugEnabled()) {
_Entry.LOG.debu
The default eogenerator templates use generics. NSArray/Set/etc is
only generic in WO 5.4 or Project Wonder. If you are using WO 5.3
without Wonder, then your NS* is not generic and cannot use the
generic templates, so you must use the 1.4 templates.
ms
On Jun 23, 2008, at 11:33 AM, Patr
I'm converting an old Xcode project to WOLips (using Tiger, java 1.5,
Eclipse 3.3.2, WOLips 3.3.5266, and WO 5.3.3).
I reached the point where I made a change to my model which resulted
in velocity EOGenerator being run, and now I have a bunch of code
that won't compile. I'm getting:
