Eclipse Community Forums: M2T (model-to-text transformation) » does an eclipse project clean delete the jet2java sources ?

Home » Modeling » M2T (model-to-text transformation) » does an eclipse project clean delete the jet2java sources ?

does an eclipse project clean delete the jet2java sources ? [message #44262]

Fri, 18 April 2008 07:38

Eclipse User

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.

Re: does an eclipse project clean delete the jet2java sources ? [message #44325 is a reply to message #44262]

Sat, 19 April 2008 07:28

Eclipse User

Edoardo:

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.

Paul

"Edoardo Comar" <ecomar@uk.ibm.com> wrote in message
news:fua189$9ur$1@build.eclipse.org...
> 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.

Re: does an eclipse project clean delete the jet2java sources ? [message #44387 is a reply to message #44325]

Mon, 21 April 2008 09:01

Eclipse User

Paul,
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.

cheers

Paul Elder wrote:
> Edoardo:
>
> 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.
>
> Paul
>
> "Edoardo Comar" <ecomar@uk.ibm.com> wrote in message
> news:fua189$9ur$1@build.eclipse.org...
>> 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.
>
>

Re: does an eclipse project clean delete the jet2java sources ? [message #44644 is a reply to message #44387]

Thu, 24 April 2008 21:51

Eclipse User

Edoardo:

I'll take a look.

Paul
"Edoardo Comar" <ecomar@uk.ibm.com> wrote in message
news:fui37j$e5p$2@build.eclipse.org...
> Paul,
> 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.
>
> cheers
>
> Paul Elder wrote:
>> Edoardo:
>>
>> 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.
>>
>> Paul
>>
>> "Edoardo Comar" <ecomar@uk.ibm.com> wrote in message
>> news:fua189$9ur$1@build.eclipse.org...
>>> 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.
>>

Previous Topic:	Accessing set variable in Java as String
Next Topic:	multivalued attributes

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 16 09:23:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter