|Re: does an eclipse project clean delete the jet2java sources ? [message #44644 is a reply to message #44387]
||Thu, 24 April 2008 21:51
| Paul Elder
Registered: July 2009
I'll take a look.
"Edoardo Comar" <firstname.lastname@example.org> wrote in message
> I think a clean should really delete everything that's derived.
> I noticed the prob because I was trying different builds (because of the \
> escaping) and I was expecting my generated code to change when it didn't.
> It took a manual deletion of the jet2java files to get new java files
> generated and subsequently see the difference in my generated code.
> Paul Elder wrote:
>> JET does not just empty the jet2java directory on a clean. It will only
>> remove a file if JETs saved state indicates that the file was generated
>> from a JET template.
>> In thinking about it, clean could be more agressive. It could remove all
>> files marked as 'derived' in the jet2java folder.
>> But, if you are sure that you have included hand written code in
>> jet2java, you can just delete all of its contents by hand and rebuild.
>> Leave the jet2java folder itself, the JDT starts issuing errors if you
>> delete it.
>> "Edoardo Comar" <email@example.com> wrote in message
>>> As I was changing jet releases by switching IDE installations over the
>>> same workspace I noticed that maybe this is not the case, while sure an
>>> eclipse clean and rebuild workspace should scrap the jet2java classes
>>> and regenerate them from the jet templates.
Powered by FUDForum
. Page generated in 0.02700 seconds