Re: [tools-pmc] Xtend (was: Xtend2)

[Sven Efftinge <sven@xxxxxxxxxxx>]

We can use 'org.eclipse.xtend'. As we have to rename the bundles anyway we can make sure that we don't introduce a
bundle name conflicting with a bundle name from the old version. 
Thank you Mike for suggesting this and make us think about it once more :-)

Cheers,
Sven

On Dec 15, 2011, at 5:12 PM, Sven Efftinge wrote:

> 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.
>> 
> 
> _______________________________________________
> tools-pmc mailing list
> tools-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tools-pmc