Closed GoogleCodeExporter closed 8 years ago
Note that this most likely requires issue 367 as well.
We will have to see how to do the timing - I plan to prepare an initial Eclipse
SmartHome contribution in the next few weeks. It is probably best if you take
this (already under org.eclipse namespace) as a basis and the result of your
work could then be merged in the Eclipse project once it is through the IP
review.
What do you think?
Original comment by kai.openhab
on 15 Nov 2013 at 10:23
I didn't take a closer look at the Xtext 2.5 dependencies, but normally Xtext
is compatible to older Eclipse platform releases. So an upgrade to Kepler is
not a requirement. I think we can keep these issues separated.
Anyway, in order not to endanger the initial SmartHome release it's reasonable
to perform the upgrade on a branch/fork and pull/merge it after the release.
I don't know if it's a problem for git to merge if the directories are
refactored fundamentally. So it might be an option to start earlier (using a
fork).
Original comment by oliver_l...@gmx.de
on 15 Nov 2013 at 10:38
> I don't know if it's a problem for git to merge if the directories are
refactored fundamentally
I am pretty much sure that this would be a problem. So let us discuss details
in Kiel :-)
Original comment by kai.openhab
on 15 Nov 2013 at 10:40
Yes, we'll do so. In the meantime I'm going to fix some smaller designer
related issues which do not impact the openhab runtime.
Original comment by oliver_l...@gmx.de
on 15 Nov 2013 at 10:43
[deleted comment]
[deleted comment]
[deleted comment]
Issue migrated to https://bugs.eclipse.org/bugs/show_bug.cgi?id=423502.
Original comment by kai.openhab
on 7 Dec 2013 at 8:44
Original issue reported on code.google.com by
oliver_l...@gmx.de
on 15 Nov 2013 at 10:17