Re: Problems with EOGenerate on Windows

From: Henrique Prange (hprang..mail.com)
Date: Wed Sep 13 2006 - 15:59:59 EDT

  • Next message: Henrique Prange: "Instance variable not found in Main class (only with incremental build)"

    Hi Mike,

    Thank you. If I have some time on the weekend I'll try to build WOLips
    and debug on my machine.

    Bests,

    Henrique

    Mike Schrag wrote:
    > If anyone wants to tab a stab at fixing this, you can look at
    > PathUtils.getRelativePath -- it's almost certain that it doesn't
    > consider that a path that starts with "C:". We should log a bug with
    > Microsoft to stop using "C:" :)
    >
    > I committed a modified version of PathUtils to make it easier to debug
    > (including a main method), I just don't have the energy at the moment to
    > startup parallels and debug this in Windows (which is what has to
    > happen, because the Mac just chokes in general on C: style paths)
    >
    > ms
    >
    > On Sep 13, 2006, at 5:17 AM, Phillip Dupuy wrote:
    >
    >> We won't be generating our EO classes this way just yet! We were just
    >> interested in trying to get Entity Modeler/EOGenerate working on Windows.
    >> For now we'll continue using the ant "exec" task (as described in
    >> /eogenerator/README) which works just fine.
    >>
    >> Phillip
    >>
    >> -----Original Message-----
    >> From: Henrique Prange [mailto:hprang..mail.com]
    >> Sent: 12 September 2006 18:22
    >> To: woproject-de..bjectstyle.org
    >> Subject: Re: Problems with EOGenerate on Windows
    >>
    >>
    >> Hi Phillip,
    >>
    >> Thanks. It works! However, I’ll stay using the custom builder to do this
    >> job integrated with Eclipse.
    >>
    >> Bests,
    >>
    >> Henrique
    >>
    >> Phillip Dupuy wrote:
    >>> Hi Henrique,
    >>>
    >>> We've been having exactly the same problem using almost exactly the same
    >>> configuration (we are using WO 5.2.3).
    >>>
    >>> My colleague Lance French has found a temporary workaround thus -
    >>>
    >>> 1. Edit your xxx.eogen file by removing the 'weird' drive prefix from
    >>> the -model argument e.g. 'C:my.eogen' becomes 'my.eogen'.
    >>>
    >>> 2. Re-name your xxx.eogen file to xxx.bat.
    >>>
    >>> 3. Run xxx.bat from the command line.
    >>>
    >>> Phillip Dupuy
    >>>
    >>> -----Original Message-----
    >>> From: Henrique Prange [mailto:hprang..mail.com]
    >>> Sent: 12 September 2006 16:02
    >>> To: woproject-de..bjectstyle.org
    >>> Subject: Problems with EOGenerate on Windows
    >>>
    >>>
    >>> Hi all,
    >>>
    >>> I’m trying to use the WOLips Tools -> EOGenerate option without success.
    >>> No files are generated and no feedback is provided neither in error log
    >>> nor in the console and in the progress views.
    >>>
    >>> Here is the content of MyEOModel.eogen file generated by WOLips:
    >>>
    >>> C:\Program Files\EOGenerator\eogenerator.exe -destination src -java
    >>> -javaTemplate JavaSourceERX52.eotemplate -model C:MyEOModel.eomodeld
    >>> -packagedirs -subclassDestination src -subclassJavaTemplate
    >>> JavaSubclassSourceEOF5.eotemplate -templatedir "C:/Program
    >>> Files/EOGenerator/Templates" –verbose
    >>>
    >>> I think that the segment “-model C:MyEOModel.eomodeld” is weird, since
    >>> MyEOModel.eomodeld isn’t in the C: root folder. Is it expected to
    >>> happen?
    >>>
    >>> I’m doing something wrong?
    >>>
    >>> System Configuration:
    >>> -Windows XP
    >>> -Eclipse 3.2
    >>> -WOLips 2.0.0.3118
    >>> -WebObjects 5.2.4
    >>> -EOGenerator 1.7
    >>>
    >>> Thanks,
    >>>
    >>> Henrique
    >>>
    >>> PS.: I’ve tried to remove “C:” from “-model C:MyEOModel.eomodeld” but it
    >>> doesn’t work too.
    >>>
    >>> PS 2.: I've tried EOGenerate on Mac and it works.
    >>>
    >>>
    >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    >>> This message is intended only for the addressee and may
    >>> contain information that is confidential or privileged.
    >>> Unauthorised use is strictly prohibited and may be unlawful.
    >>>
    >>> If you are not the addressee, you should not read, copy,
    >>> disclose or otherwise use this message, except for the
    >>> purpose of delivery to the addressee. If you have received
    >>> this in error, please delete and advise us immediately.
    >>>
    >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    >>> Although Company Watch makes every reasonable effort to keep
    >>> its network and systems free from viruses, the company
    >>> accepts no responsibility for computer viruses transmitted
    >>> through this mail or in any attachments. It is your
    >>> responsibility to virus scan any attachments we send to you.
    >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    >>>
    >>>
    >>>
    >>
    >>
    >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    >> This message is intended only for the addressee and may
    >> contain information that is confidential or privileged.
    >> Unauthorised use is strictly prohibited and may be unlawful.
    >>
    >> If you are not the addressee, you should not read, copy,
    >> disclose or otherwise use this message, except for the
    >> purpose of delivery to the addressee. If you have received
    >> this in error, please delete and advise us immediately.
    >>
    >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    >> Although Company Watch makes every reasonable effort to keep
    >> its network and systems free from viruses, the company
    >> accepts no responsibility for computer viruses transmitted
    >> through this mail or in any attachments. It is your
    >> responsibility to virus scan any attachments we send to you.
    >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    >>
    >>
    >
    >



    This archive was generated by hypermail 2.0.0 : Wed Sep 13 2006 - 16:00:39 EDT