Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344301 - [Xtend] avoid removing xtend-gen folder
Summary: [Xtend] avoid removing xtend-gen folder
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: SR2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-29 11:39 EDT by Maxim Frolov CLA
Modified: 2017-09-19 17:17 EDT (History)
5 users (show)

See Also:
sven.efftinge: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maxim Frolov CLA 2011-04-29 11:39:52 EDT 
The Xtend2 builder removes each time the xtend-gen folder recursively including non-Java files and folders like for example Subversion .svn folders. 

The generated java files in xtend-gen folder get deleted from VCS as well if one commits changes in VCS.

This is a problem if one uses Maven for executing generator: Java classes generated by Eclipse Xtend2 builder have to be checked in.
Comment 1 Sebastian Zarnekow CLA 2011-05-04 12:50:31 EDT 
Scheduled for RC1 since this one renders Xtend unusuable for CVS and SVN users who want / have to commit their generated code into the repo.
Comment 2 Sven Efftinge CLA 2011-05-11 10:21:32 EDT 
who's working on this?
Comment 3 Sebastian Zarnekow CLA 2011-05-13 10:49:08 EDT 
I pushed (something) to master.

Unfortunately I've not been able to test the fix in a real world scenario. Please reopen the ticket as soon as possible if the problem persists.
Comment 4 Karsten Thoms CLA 2011-10-06 15:05:10 EDT 
I observed today this problem with a Subversion controlled project.

Steps to reproduce:
- Check in an Xtext project including xtend-gen into Subversion
- Have a package with just one .xtend file
- Check in the generated Java file
- produce a compile error in the Xtend file

=> The generated Java file is removed, and the folder is marked obstructed for subversion. .svn metainformation was accidently removed.
Comment 5 Sebastian Zarnekow CLA 2011-10-07 03:05:45 EDT 
Did you configure svn as the team provider for the given project? Which subversion plugin did you use?
Comment 6 Karsten Thoms CLA 2011-10-07 05:02:31 EDT 
How can the team provider project set project specific? The project is attached to Subversion.

The subversion plugin used is Subclipse 1.4.8 with JavaHL 1.5.7
Comment 7 Sebastian Zarnekow CLA 2011-10-07 05:06:12 EDT 
(In reply to comment #6)
> How can the team provider project set project specific? The project is attached
> to Subversion.

The question was whether Eclipse knew about the subversion project or whether you imported it into the workspace without a team provider configuration. Sorry about the unclear question.

> The subversion plugin used is Subclipse 1.4.8 with JavaHL 1.5.7

Ok.
Comment 8 Karsten Thoms CLA 2011-10-07 09:02:15 EDT 
So, to make my answer also clear: Eclipse knows about the Subversion configuration. The project and the generated xtend files are marked with Subversion information and the folder is marked obstructed also in Eclipse (with red cross icon) when the generated Xtend file is removed.
Comment 9 Sebastian Zarnekow CLA 2011-10-09 12:11:26 EDT 
(In reply to comment #8)
> So, to make my answer also clear: Eclipse knows about the Subversion
> configuration. The project and the generated xtend files are marked with
> Subversion information and the folder is marked obstructed also in Eclipse
> (with red cross icon) when the generated Xtend file is removed.

Which Xtext build do you use?
Comment 10 Sebastian Zarnekow CLA 2011-10-11 05:54:29 EDT 
(In reply to comment #9)
> Which Xtext build do you use?

Ping
Comment 11 Karsten Thoms CLA 2011-10-11 07:35:44 EDT 
It was Xtext 2.0.1 final.
Comment 12 Sebastian Zarnekow CLA 2011-10-11 07:36:55 EDT 
(In reply to comment #11)
> It was Xtext 2.0.1 final.

Could you do me a favor and double check with one of the latest nightlies (hudson is unfortunately down, though)?
Comment 13 Karsten Thoms CLA 2011-10-11 09:44:05 EDT 
I do not have the environment in which it occured, it was at customer's site. But I'll try to reproduce it soon.
Comment 14 Sebastian Zarnekow CLA 2011-10-12 09:27:15 EDT 
(In reply to comment #12)
> (In reply to comment #11)
> > It was Xtext 2.0.1 final.
> 
> Could you do me a favor and double check with one of the latest nightlies
> (hudson is unfortunately down, though)?

Hudson is back again :-)
Comment 15 Sven Efftinge CLA 2011-10-25 02:48:25 EDT 
I'm almost sure this is fixed with the introduction of the complier preferences. Please reopen if I'm wrong.
Comment 16 Karsten Thoms CLA 2017-09-19 17:05:42 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 17 Karsten Thoms CLA 2017-09-19 17:17:35 EDT 
Closing all bugs that were set to RESOLVED before Neon.0