On Thu, Aug 21, 2014 at 9:39 AM, Francois Green
<
francoi...@gmail.com> wrote:
> I've started playing with the Ceylon 1.1.0.v20140819 Dev IDE and I need some
> guidance. I would like to know how to use Ceylon with an existing Java EE
> project in light of the changes brought about by 370. I had expected being
> able to "Add Ceylon Nature" to an old project and things would just work
> (sort of like Scala, Xtend or whatever).
No, well it's not quite that straightforward because Ceylon has:
1. a well-defined module system, and
2. a system of reified generics and a metamodel which requires some
initial bootstrapping.
So integration into a foreign module system like Java EE or OSGi or
whatever is a task that involves work. It's not a conceptually
difficult task, but it does need doing.
That might sound like a bit of a disadvantage of Ceylon until you
realize that once we actually sit down and do this work, we can do
lots of potentially very cool stuff by leveraging the information in
the Ceylon module descriptor. (E.g. our compiler now generates .cars
with built-in OSGi and maven metadata with no intervention from the
user.)
Integrating Ceylon in Java EE is very high on our priority list now,
but it's not going to make it into 1.1, because we want to do it
properly and make it awesome.
--
Gavin King
ga...@ceylon-lang.org
http://profiles.google.com/gavin.king
http://ceylon-lang.org
http://hibernate.org
http://seamframework.org