Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368963

Summary:	[Xtend] Include headless feature for Xtend SDK
Product:	[Tools] Xtend	Reporter:	Vlad Dumitrescu <vladdu55>
Component:	Core	Assignee:	Project Inbox <xtend-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	sven.efftinge
Version:	2.2.0
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Vlad Dumitrescu

2012-01-18 08:52:56 EST

For building plugins with Buckminster, the required SDKs must not have any UI dependency. The usual way to solve that (when possible) is to have a headless feature that only includes what is required for the builder to run.

If that is possible for Xtend, please build a headless feature too.

Comment 1 Sven Efftinge

2012-01-18 08:54:57 EST

Just for clarification.

Do you ask for 
1) a feature including everything needed to run the compilation in a headless buckminster build
2) a feature including only the runtime libs to compile generated java sources against

Comment 2 Vlad Dumitrescu

2012-01-18 09:00:43 EST

It's number 1: a feature including everything needed to run the compilation in a headless buckminster build

Comment 3 Sven Efftinge

2013-09-12 08:09:45 EDT

We've tried to get rid of UI dependencies in the builder, but it is unfortunately not possible without major refactoring and API breakage.

We (i.e. Dennis) use a workaround in our builds, where we launch an Eclipse Application on the to be built workspace, That one then rebuilds the entire workspace.

Comment 4 Sven Efftinge

2013-09-12 08:10:21 EDT

changed from RESOLVED to CLOSED

Comment 5 Vlad Dumitrescu

2013-09-12 08:14:06 EDT

That's too bad. 

My workaround is to store the generated Java files in version control.

Comment 6 Sven Efftinge

2013-09-12 09:05:16 EDT

(In reply to Vlad Dumitrescu from comment #5)
> That's too bad. 

Yes, I wished we could solve this one.

> 
> My workaround is to store the generated Java files in version control.

We also do that but we regenerate so that the trace files are created and the bytecode gets enhanced (for debugging).

Comment 7 Vlad Dumitrescu

2013-09-12 09:09:33 EDT

Maybe in version 2?

Good point about the trace files; it should work to just add those to version control too, right?

Thanks!

Comment 8 Sven Efftinge

2013-09-12 09:12:03 EDT

(In reply to Vlad Dumitrescu from comment #7)
> Maybe in version 2?

The problematic code is in Xtext and is public API.
We would have to make an incompatible Version 3.

Given the very few users of buckminster I doubt that we'Re going to do that.

> Good point about the trace files; it should work to just add those to
> version control too, right?

Yes, but the compiled Java classes need to be enhanced. That doesn't happen automatically and without that debugging won't work.

Comment 9 Vlad Dumitrescu

2013-09-12 09:18:24 EDT

I see. So I suppose that using Tycho and Maven doesn't have the same problem as Buckminster?

Okay, thanks for the explanation regarding debugging. I'll make a note of it.

Comment 10 Sven Efftinge

2013-09-12 09:28:15 EDT

(In reply to Vlad Dumitrescu from comment #9)
> I see. So I suppose that using Tycho and Maven doesn't have the same problem
> as Buckminster?

Yes, it works nicely with tycho / maven.