[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
It's mainly because the bundles are marked as 'singletons', i.e. equinox won't activate two of them in two different versions. That
makes it impossible to have e.g. a smooth migration scenario. And also Xtext has some legacy references to Xtend, which we cannot fully replace without compatibility issues.
But we might be able to work around these issues.
I'll check wit my team what kind of issues that could cause and how we can deal with them.
Thanks,
Sven
On Dec 15, 2011, at 4:52 PM, Mike Milinkovich wrote:
> OK, I must be an idiot. Why won't bundle versioning allow you to retain the
> org.eclipse.xtend namespace in its new home?
>
>> -----Original Message-----
>> It's because the namespace (i.e. package name) org.eclipse.xtend is
> already
>> taken by the former version of Xtend, i.e. the one from
>> modeling.m2t.xpand.
>> It would be perfectly ok to call the project simply 'Xtend' (and resp.
>> tools.xtend) if that doesn't prevent us from using the namespace
>> org.eclipse.xtend2.
>
