Acceleo 2

With Juno's arriving to the end of the release cycle Eclipse Day's are popping up everywhere in the world. If you are not too far from France, you should consider joining us next week for Eclipse Day ToulouseGreat content, very low price (20€) and ... [More] Toulouse is so sunny it can only be nice !I will be there presenting Eclipse Modeling. A 101 session leading you to the jungle of one of the most diverse top level project in Eclipse, describing some of the main components and how you can use them in your day to day work.Register now, this event takes place next week!It is said the west of France is less sunny but I'm pretty sure its a myth spread by the Bretons frighten tourists.   The 2012 breizhcamp will be the occasion to confirm my belief.This is a Java/Webapps event during two days with more than 50 speakers ! I will be representing Eclipse there along with Stéphane. We will give an Acceleo tutorial.And here is the Breizh Camp trailer : The EclipseCon Europe call for paper is out ! You should consider to start preparing your submission.  The  conference tracks are :Eclipse Technology. Building Industry Solutions.Community and Collaboration.OSGi.Other Cool Stuff.Lets make this the best EclipseCon ever! [Less]

Last month, Julien, from the INRIA Aoste team, has presented the RT-Simex project to the FSE conference (http://fse18.cse.wustl.edu/). The slides are available here : http://www.slideshare.net/fthomasfr/fsertsimex.

During the last CSDM 2011 conference, I have presented our work made in the IMOFIS project. IMOFIS was an R&D project with Renault, Alstom Transport, Systerel, UTC, CEA-List and Obeo to develop an environment that assists safety engineers to ... [More] analyse and verify their systems. This project ended on October 25 2011. In this project, we have developed a metamodel and a tool, named Alea ToolKit, to capture both parts of the system designs and parts of the safety analyses needed to build a critical systems. For example, one system studied in this project is the Communication Based Train Control  (CBTC). To build such systems, typical process is dual : on one side the system engineering and in other side the safety engineering. The first one leads to build a safe system. The second leads to verify that the system is build in safety. Between this two engineerings, the exchanges are models, documents and mainly requirements. System have to manage requirements (refine, satisfy, derive it). Safety has to tag requirements as safety ones. Typical system engineering process One key problematic in such process is to be able to synchronize system and safety world. One subset of needs is : the adaptability, i.e to provide a tool and methodology usable for several projects and even several domains such as railway and automotive ones.  the interoperability, i.e. to be able to reference system modeling elements to describe the safety analyses, the consistency, i.e. to provide facilities in order to manage several safety modeling levels (Preliminary Hazard Analysis, Fault Tree, FMEA). We want to help user to manage the consistency among thus abstraction levels, the traceability, i.e. to be able to compute links among engineerings and to use those links for navigation. A set of needs explored in IMOFIS Hence,to fulfill those needs, we have explored the use of a viewpoint based approach with Obeo Designer. The key idea is to capitalize concepts in a generic/general safety metamodel and to provide different views to specialize the use of this generic metamodel for a specific concerns : a specific abstraction level or a specific domain. This metamodel is build on the the Eclipse Modeling Framework in order to achieve the interoperability with other system metamodels (SysML in our case). The views are implemented in a viewpoint based-engine : Obeo Designer. The resulting modeling framework is the Applied metamodeL for safEty Analyses ToolKit. To illustrate such a tool, let's illustrate on the CBTC  example. Firstly, we check the correct viewpoints. In a viewpoint based-approach, user choose the viewpoint to load. Then, let's take a look to the system design from the SysML viewpoint. From SysML, user can navigate to the safety analyses. For example, the F2 function is used in two safety analyses : a cause analysis (Fault tree analysis) and an accident case analysis (Preliminary Hazard Analysis). In fact, the safety engineer described the accident case from the SysML model : i.e. he references the SysML CTBC Block and the F2 function from the SysML model. Hence, the safety engineer interoperate with the system design in order to build his analysis. From the Alea ToolKit point of view, this scenario is "just" a graphical view on a global enhanced fault tree. The viewpoint tool manage the consistency between this event sequence view and the cause analysis view represented as a fault tree. The following picture is the projection of the previous scenario from a fault tree point of view.   The viewpoint manage also the traceability links between the views. For example, the traceability companion allow to navigate among the safety views. From a second accident case for the excessive speed hazard, user can navigate to the previous scenario. Hence, viewpoint based approach allow to provide an integrated modeling framework gathering Safety and System concerns. It improves information search, communication (before many documents were parsed) and coherency among safety/system analyses. This approach is not a new set of methods for safety analyses. It doesn't take into account all the safety activities but PHA, SHA and FMEA modeling at the system level.  Next steps are bridges : a safety viewpoint is not only graphical representations, but this is also a set of filters and information synchronizations for specific concerns. Hence my next work is to enhance those graphical viewpoints in order to connect business tools such as my AltaRica editor. This is another R&D story ! If you want more information, a complete presentation of this work is available here [Less]

If you are in Washington for EclipseCon 2012, don't miss the "hot new product showcase".It will start Wednesday, at 17:50.You will see plenty of demos of new exciting technologies created with Eclipse projects.Last year, I really enjoy it ... [More] because:it's very easy to speak with the guys who created these products, you are not stress because of the beginning of a talkyou can see products, while talks are main focus on technologiesthe vibes is good, as there is a reception at the same place This year, I'm proud to present there our DSL workbench: Obeo Designer.One of our challenge we would like to do with our visitors: create in live, with only several minutes, a nice looking graphical designer customized with the visitor's choices.To explain its features in a funny way, I made this original presentation:.prezi-player { width: 550px; } .prezi-player-links { text-align: center; } [Less]

Hi, EEF is preparing to move to Git ! We have already set up the repository, and we will mark the CVS read only right after the 1.1 Release. EEF should be available soon in GitHub. http://git.eclipse.org/c/eef/org.eclipse.eef.git/

We are pretty active in Eclipse:building the technology to generate code or text from modelslowering the "system" versus "doc" barrierproviding a cool UI generation technology to pimp your editorsenabling model to model transformationsbuilding ... [More] the Modeling packageenabling team work on models using your favorite SCM making sure graphical Ecore modeling is still a reality (HELP WELCOME)mentoring new projectsreporting and fixing bugs on several other projects.organizing or sponsoring Eclipse related eventsI'd love to show all these things during EclipseCon, especially considering things are happening for  every single project listed here(*). There is just not enough time and many other interesting things to cover in such a short event but feel free to come and talk to us during the conference. On the other hand we are giving several talks worth mentionning :You did not knew Acceleo was an implementation of an OMG standard ?  Stéphane will present it during the Eclipse/OMG Workshop on Sunday.Meet Stéphane on Sunday, 15:55– 16:20Eclipse is a best platform to build tools. Eclipse Modeling makes things even easier, but why would you need tools ? Aren't they available already  ? Well, generic tools suitable for any use case are hard to make,  you might want to use a given technology and not having any tool.  Good news is Eclipse Modeling enables you to build a dedicated tool in no time. We'll start the EclipseCon conference with a tutorial so that you learn how, leading you through an example tool to build a web app powered by  localstorage, Backbone.js and, JQuery.We're preparing the tutorial content in a way that you should be able to replay or present it when you'r back home. All the steps are  documented through eclipse cheatsheets and you'll get an all-in-one update-site.Meet Stéphane and me on Monday, 13:00 – 16:00 in Lake Anne B If you're interested in industrial collaboration to provide long term and very long term support for Eclipse technologies, the Polarsys talk on Tuesday is for you.Meet Gael on Tuesday, 17:00 – 17:50 in Reston Suites BIf you're more interested in technologies, modularity and dynamicity, Mikael is sharing an experiment on bringing EMF in a multi-tenant and dynamic world while trying to reduce API breakages to a minimum.3MF : EMF To the infinity ... and beyond !Meet Mikael on Tuesday, 17:00 – 17:50 in Lake ThoreauIf you're into Agile and ALM and don't want to give-up on design documentation, Alex will present the Mylyn Intent project :Meet Alex on Wednesday, 10:30 – 11:15 in Regency Ballroom AIn a nutshell, it's gonna be legendary :)(*) I guess I'll should also blog more to share what's happening. [Less]

Hi, Following David's request [1], I modified the promotion script used by EEF and other obeo's tycho builds in order to be more friendly with the Eclipse's servers infrastructure :) I modified the pom.xml file for the update site project, adding a ... [More] post-step phase generating a properties file and copying 2 files : - a promote.xml ant script, - a p2.xsl xslt file. Then when I connect to eclipse servers, i am able to run the ant script that do these steps : - copy the zipped update site to correct drops location, and renaming it using the properties given at the launch of the build ( Type, Alias ) - unzip the same update site to updates location, - apply the xslt transformation to the p2 metadatas in order to activate updates stats and p2.mirrorsURL indication, - copy the p2.index files in correct location. if you are interested in this script for your tycho build, take a look at : http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.emf/org.eclipse.emf.eef/releng/org.eclipse.emf.eef.update/?root=Modeling_Project  [1] http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07400.html [Less]

The next version of Acceleo will introduce a number of improvements of its existing features, one of its most important, the automatic builder, being entirely re-written in order to get rid of legacy code and improve the user experience. This also ... [More] comes with a much better experience for users that need to build their Acceleo generators in standalone, through maven or tycho. More news on this are available on the bugzilla and Stephane's latest post.One of the least visible features, yet one I find among the most interesting aspects of the Acceleo code generator, is the traceability between the generated code, the model used as input of the generation, and the generator itself. Basically, you always know where that esoteric line of code came from : which part of the generation template generated it, and which model element triggered its generation.This feature has known a series of improvements as we used it intensively with the UML to java generator. We are now confident that we can record and display accurate information even for some of the most complex use cases. This generator isn't the most complex generator we could write with Acceleo, but it is quite complete nonetheless. Here are some examples of what the Traceability can provide to architects developping their code generators :Determine which model element triggered the generation of a line of codeOn the left-hand side, a file that has been generated. On the right-hand side, an editor opened as result of using the action "open input" : the model is opened and the exact element that was used to generate the part of code is selected.Find the part of a generator that created a given part of the codeOn the left-hand side, the same generated file as above. On the right-hand side, the result of using the "open generator" action : the Acceleo generator which generated that selected part of the code is opened, with the exact source expression selected.Real-time SynchronizationThese are but a few of the features that can be derived from the synchronization between code, model, and generators. Some more examples include : previewing the result of a re-generation, incremental generation, round-trip (updating the input model according to manual changes in the output generated code)...Most of these features are better seen in video to get an idea. If you want to see some of them in action, some more flash videos of what traceability can do for you are available on the Obeo network (though a free registration is required). [Less]

With the release of the new Acceleo stand alone front end for the compilation of Acceleo modules, I’ve started to work on a brand new maven integration in Acceleo. Currently in Acceleo, if you need to build Acceleo modules with maven you have to use ... [More] a Tycho based build with a java class generated by Acceleo to tweak the build (for example to register the metamodel(s) used in the modules). This Tycho based build will always produce an Eclipse plugin as a result. The next major release of Acceleo will have a maven plugin dedicated to the compilation and it will bring several key improvements. Firstly, the new compilation front end brings a completely stand alone compilation. Those who want to build their Acceleo modules without having to build an Eclipse plugin will be able to do so. Secondly, this new front end support more complex project structures (with for example, multiple output folders in a same project). Thirdly, you will have the ability to contribute a class to influence the uris of the dependencies in the saved files (for example, change all the uris of the dependencies to other module to “platform:/plugins” uris that are more “eclipse plugin” friendly). Finally, it also features an improved resolution of the dependencies of a project with several options. Your project will be able to have a dependency to Acceleo modules in another project (that should have been previously compiled). A valid Acceleo project is just a directory on the file system with at least one “source” sub-directory and one “output” sub-directory (no need of an Eclipse nature or anything like that). This first solution is fine as long as you have the source code of the other modules but sometime you need to build something with the dependencies in jars. The maven plugin for Acceleo will let you declare a dependency to a jar containing already compiled Acceleo modules by using: The absolute path of the jar. Ex: C:\…\myJar.jar The path of the jar relative to the project built. Ex: ${project.basedir}\lib\myJar.jar The groupId and the artifactId of the jar resolved by maven  (the version of the jar is optional since some version number includes the date of the build and therefore change often). Ex: myGroupId:myJar:myVersion The name of an Eclipse bundle resolved by Tycho preceding by “p2.eclipse-plugin” only in a Tycho based build (“p2.eclipse-plugin” is the groupId of all the dependencies resolved by Tycho). Just like the previous use case, the version of the jar is optional too. Ex: p2.eclipse-plugin:myJar:myVersion For those who want to have a look at this new maven based build for Acceleo, you can find its source code on github.com and you can test it with a simple pom.xml like this one. [Less]

With the release of the new Acceleo stand alone front end for the compilation of Acceleo modules, I’ve started to work on a brand new maven integration in Acceleo. Currently in Acceleo, if you need to build Acceleo modules with maven you have to use ... [More] a Tycho based build with a java class generated by Acceleo to tweak the build (for example to register the metamodel(s) used in the modules). This Tycho based build will always produce an Eclipse plugin as a result. The next major release of Acceleo will have a maven plugin dedicated to the compilation and it will bring several key improvements. Firstly, the new compilation front end brings a completely stand alone compilation. Those who want to build their Acceleo modules without having to build an Eclipse plugin will be able to do so. Secondly, this new front end support more complex project structures (with for example, multiple output folders in a same project). Thirdly, you will have the ability to contribute a class to influence the uris of the dependencies in the saved files (for example, change all the uris of the dependencies to other module to “platform:/plugins” uris that are more “eclipse plugin” friendly). Finally, it also features an improved resolution of the dependencies of a project with several options. Your project will be able to have a dependency to Acceleo modules in another project (that should have been previously compiled). A valid Acceleo project is just a directory on the file system with at least one “source” sub-directory and one “output” sub-directory (no need of an Eclipse nature or anything like that). This first solution is fine as long as you have the source code of the other modules but sometime you need to build something with the dependencies in jars. The maven plugin for Acceleo will let you declare a dependency to a jar containing already compiled Acceleo modules by using: The absolute path of the jar. Ex: C:\…\myJar.jar The path of the jar relative to the project built. Ex: ${project.basedir}\lib\myJar.jar The groupId and the artifactId of the jar resolved by maven  (the version of the jar is optional since some version number includes the date of the build and therefore change often). Ex: myGroupId:myJar:myVersion The name of an Eclipse bundle resolved by Tycho preceding by “p2.eclipse-plugin” only in a Tycho based build (“p2.eclipse-plugin” is the groupId of all the dependencies resolved by Tycho). Just like the previous use case, the version of the jar is optional too. Ex: p2.eclipse-plugin:myJar:myVersion For those who want to have a look at this new maven based build for Acceleo, you can find its source code on github.com and you can test it with a simple pom.xml like this one. [Less]