I'm assuming you guys are running EOGenerate... manually? Do you
have WOLips=>Build=>Auto EOGenerate on Build (which is on by
default)? If so, then what you're seeing is that when you save your
model, WOLips is detecting that you changed the model and then
running eogenerator as part of the build process (which obviously
then doesn't want to complain if nothing broke). Then when you run
it manually, "nothing changed". Just a guess ...
ms
On May 18, 2007, at 7:02 AM, Kieran Kelleher wrote:
> This just happened to me last night for the first time last night.
> eogen actually did update the java class files even though it said
> no changes..... I thought that I was losing my mind, so I had to
> reach for a Guinness to try and correct my mind.
>
> On May 18, 2007, at 5:06 AM, Lachlan Deck (JIRA) wrote:
>
>> EOGenerate... not capturing output
>> ----------------------------------
>>
>> Key: WOL-440
>> URL: http://issues.objectstyle.org/jira/browse/
>> WOL-440
>> Project: WOProject/WOLips
>> Issue Type: Bug
>> Affects Versions: 2.0.0.* (unreleased please specify)
>> Environment: WOLips 2.0.0.4018
>> Reporter: Lachlan Deck
>> Priority: Trivial
>>
>>
>> Simply tells me that there were 'no changes'... but there were
>> changes (as evidenced by svn)
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the
>> administrators: http://issues.objectstyle.org/jira/secure/
>> Administrators.jspa
>> -
>> For more information on JIRA, see: http://www.atlassian.com/
>> software/jira
>>
>>
>
This archive was generated by hypermail 2.0.0 : Fri May 18 2007 - 07:37:02 EDT