[news.eclipse.modeling.tmf] Re: Problem: different languages are using t

[Sven Efftinge <sven.efftinge@xxxxxxxxx>]

Hi Michael,

> If I call (as suggested by the wizard and
> enforced by warnings in the wizard) my project:
>   org.xtext.example.mydsl
> and the language
>   org.xtext.example.MyDsl
> then it puts stuff into the package
>   org.xtext.example
> which is against the java plugin conventions.

Why is that?

> The wizard complains if I call my project:
>   org.xtext.example.mydsl
> and the language (note the .mydsl.)
>   org.xtext.example.mydsl.MyDsl

Yes, we should remove such warnings.
Could you please open a bugzilla, so we won't forget?

> But this setting use packages as I would
> expect it (that is: the all used packages
> would start with org.xtext.example.mydsl)
>
> The three examples
>   org.eclipse.xtext.example.domainmodel
>   org.eclipse.xtext.example.ecoredsl
>   org.eclipse.xtext.example.fowlerdsl
> all create packages with the same name
>   org.eclipse.xtext.example
>   org.eclipse.xtext.example.parser.antlr
>   org.eclipse.xtext.example.services
>
> Is this intentional? I would consider putting
> classes into the same packages from different
> plugins a bad idea... E.g. OSGI package imports
> does get confused if multiple project use the
> same package.

Yes, you're right. When we wrote them we didn't care too much about 
import package scenarios.
Also worth a bugzilla, I guess :-)

Cheers,
Sven

--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com