Author Topic: Problems with Forward Engineering Java code  (Read 1732 times)


  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Problems with Forward Engineering Java code
« on: October 15, 2003, 02:33:32 pm »
I'm using build 3.60.647 on Windows 2000.

I'm having several issues forward engineering Java code.  In all instances I have reverse engineered the code from an existing code base.

1. How do I get EA to not update the file modified timestamp on classes I haven't actually changed within EA?  Currently, all files get updated regardless.  This makes it hard to review changes.

2. It seems that the new build makes all interfaces abstract, regardless of whether or not they started out that way.  How do I get EA to leave my interface definitions as I made them?

Any and all help would be appreciated,



  • EA Administrator
  • EA User
  • *****
  • Posts: 195
  • Karma: +0/-0
    • View Profile
Re: Problems with Forward Engineering Java code
« Reply #1 on: October 16, 2003, 12:14:17 am »
Hi funkiwan,

1. Currently it's not possible to prevent this timestamp modification during generation.  We'll try to correct this in a future build- for the case where no updates are to be made.

2. You can fix this by modifying the default code generation template for java interfaces
a) Open the Code template editor (Cntrl+Shift+P)
b) Select java as the language
c) Select the Class Declaration template
d) Remove the line that reads:
Code: [Select]
%classAbstract=="T" ? "abstract" : ""%
e) Click save

(I think the abstract keyword is redundant now for interfaces in java- we'll look at leaving this out of the default templates in future.)

Thanks for the feedback.