Target platform definition problem about openhab-addons HOT 4 CLOSED

Can you provide a screenshot or details on what packages are concerned?

from openhab-addons.

org.eclipse.xtend
org.eclipse.xpand
org.eclipse.xtend.typesystem.emf

I did also a "Add Required Plug-ins" several times, but not everything got resolved. The initial list was empty, strangly enough

I tried to debug the Things.xtend problem but I sense that it has to be done through a proper ESH workspace. I only partially imported bundles into my workspace, but couldn't get the MWE to run to generate the necessary code. "mvn clean install" on a cloned ESH repo ran into a java heap error - I was hoping that that would put the generated classes in the appropriate directories

On 29 Sep 2014, at 22:45, Kai Kreuzer [email protected] wrote:

Can you provide a screenshot or details on what packages are concerned?

—
Reply to this email directly or view it on GitHub.

from openhab-addons.

Ok, so you only have problems as soon as you import additional ESH projects (that are not in openHAB2 repo) into your workspace. This is normal as openHAB2 target platform does not come with all the stuff you need for code generation - after all, this is already done on the ESH side and thus makes openHAB2 builds much simpler.
So if you want to work on ESH specific things, go for an ESH IDE instead (https://github.com/eclipse/smarthome/blob/master/docs/sources/development/ide.md). I know that this is not very convenient - but having to maintain many target platforms is also quite some effort. So I am not sure yet, what is the best on the long run. In general, I would openHAB2 developers expect to have no need to do changes in ESH (once this is a bit more stable).

from openhab-addons.

Yep

But removing them afterwards breaks everything for some reason

K

Sent from my iPhone

On 30 Sep 2014, at 00:01, Kai Kreuzer [email protected] wrote:

Ok, so you only have problems as soon as you import additional ESH projects (that are not in openHAB2 repo) into your workspace. This is normal as openHAB2 target platform does not come with all the stuff you need for code generation - after all, this is already done on the ESH side and thus makes openHAB2 builds much simpler.
So if you want to work on ESH specific things, go for an ESH IDE instead (https://github.com/eclipse/smarthome/blob/master/docs/sources/development/ide.md). I know that this is not very convenient - but having to maintain many target platforms is also quite some effort. So I am not sure yet, what is the best on the long run. In general, I would openHAB2 developers expect to have no need to do changes in ESH (once this is a bit more stable).

—
Reply to this email directly or view it on GitHub.

from openhab-addons.