Blog

Posted on in Blog
When you model a system, you use a specific language (meta-model) to represent information. So, you use a particular language fitted to your business needs. It may be required to specialize this model giving a precise semantics on each object, but also to rise above it through other business concepts to read, understand, exploit it better or enhance it from different viewpoints. So, you can imagine to manage a requirements model which decorates/references/plugs in a design model allowing to check that this last one is conform to the specifications.In the example below, I focus on the decoration of a UML model with a DSL (Domain Specific Language). The need was to configure a UML model (design of communicating components) and to test these configurations against code generation. Each configuration defines a combination of different and particular communication protocols to use on the connectors between components. And, of course, each protocol brings its own parameters which may be quit...

Posted on in Blog
We always intend to run our Eclipse projects as real open-source projects. Being open, transparent and so on. The Eclipse Development process forces you to do so in some way, the simultaneous release brings a bit more constraints in this regards but in the end, if you want a truly open project you'll need to do more.Let's take EMF Compare. It quickly jumped into the release train, adopted the Eclipse practices, got used by other components and had a number of major contribution.We have two main groups of adopters: the first group is comprised of end-users, which mostly have the perception the problem itself of comparing models is quite easy and it should "just works". They tend to report bugs, UI glitches, and sometime even with patches. The second group is researchers, they know the problem is not that easy and having this component enables all kind of experiments on top of models for them. They tend to use compare in contexts we never ever envisionned.We had several fairly big contri...

Posted on in Blog
We always intend to run our Eclipse projects as real open-source projects. Being open, transparent and so on. The Eclipse Development process forces you to do so in some way, the simultaneous release brings a bit more constraints in this regards but in the end, if you want a truly open project you'll need to do more.Let's take EMF Compare. It quickly jumped into the release train, adopted the Eclipse practices, got used by other components and had a number of major contribution.We have two main groups of adopters: the first group is comprised of end-users, which mostly have the perception the problem itself of comparing models is quite easy and it should "just works". They tend to report bugs, UI glitches, and sometime even with patches. The second group is researchers, they know the problem is not that easy and having this component enables all kind of experiments on top of models for them. They tend to use compare in contexts we never ever envisionned.We had several fairly big contri...

Posted on in Blog
We always intend to run our Eclipse projects as real open-source projects. Being open, transparent and so on. The Eclipse Development process forces you to do so in some way, the simultaneous release brings a bit more constraints in this regards but in the end, if you want a truly open project you'll need to do more.Let's take EMF Compare. It quickly jumped into the release train, adopted the Eclipse practices, got used by other components and had a number of major contribution.We have two main groups of adopters: the first group is comprised of end-users, which mostly have the perception the problem itself of comparing models is quite easy and it should "just works". They tend to report bugs, UI glitches, and sometime even with patches. The second group is researchers, they know the problem is not that easy and having this component enables all kind of experiments on top of models for them. They tend to use compare in contexts we never ever envisionned.We had several fairly big contri...

Posted on in Blog
Today the third milestone of the Mylyn connector for Tuleap has been released. In this new version, we have mainly worked on Mylyn Context integration, support for attachments and queries. As we’ve seen before, you start by configuring your Mylyn repository with the URL of your Tuleap trackers. Starting with this release, you can retrieve the reports saved on the Tuleap server and execute them directly from Eclipse but you can also create your own queries by defining precisely your own critera. When you open an artifact, you can use an editor parameterized by the definition of the tracker that you have created in Tuleap. This editor lets you edit your tasks directly from Eclipse. You can now freely download and upload attachments from this editor. When a task is activated, the technical artifacts that you manipulate will be saved and the Package Explorer view will be filtered to display only the artifacts relevant to your work on this task. You can also store the context of you...