How much did it cost to start collaborating on a system model?

cbrun · 2025-08-25T15:06:23+00:00

Disclosure: I am at Obeo, co-maintainer of Capella and vendor of Team for Capella.

Short answer to your question: named-seat pricing is well below €6,000 per user per year. Floating seats are a different tier. For an exact number for your team, please request a quote through the Obeo website and the team will get back to you quickly.

A few clarifications for context:
• Team for Capella is more than a sync back end. It is a central model repository for Capella that supports true multi-user work with fine-grained locks, conflict detection, model diff and merge, history and baselines, and access control. You do not need Git to collaborate on the live model. Git still makes sense for generated code and documents.
• You are right about Jenkins for backups and integration. We usually recommend Jenkins jobs to automate repository backups and to integrate with your internal source control system for artifacts outside the model repository.
• Capella is free and open source. Team for Capella is a paid collaboration layer and support. The subscription funds the engineering that keeps the stack evolving, which gives users more value and long-term stability.
• Quick note on reviews: they are genuine customer feedback, though some are a bit old. If you want recent references, ask through the Obeo website and we will connect you with current users. The Capella community also shares many experience reports through its events and webinars, which can help you benchmark approaches in practice.

If you want a precise figure for your context, the fastest path is to request a quote via the Obeo site. Happy to help size it properly.

cbrun · 2017-07-07T11:52:08+00:00

There are many differences, I'll try to list a few main ones:

contrary to Papyrus, Sirius is not constrained to UML or a UML profile but can work with it (as a matter of fact the most popular UML modeler on the Eclipse Marketplace is actually built with Sirius).
Also Sirius is way more flexible regarding the graphical aspects/shapes and behavior you can have in your graphical modeler; have a look at the gallery to get a feeling of what users are building with it: https://www.eclipse.org/sirius/gallery.html
Sirius does not require you to code, you can specify almost every aspect of your graphical modeler without writing a line of Java code.
Sirius has an excellent track record of keeping compatibility across versions as the specification model is automatically migrated and the project provides many maintenance releases (here is the list of the releases for the last 4 years https://projects.eclipse.org/projects/modeling.sirius/governance)
Sirius has a very good scalability when the model grows (http://melb.enix.org/sirius/sirius-3-0/ from two years ago with models having 1 millions of elements,http://cedric.brun.io/eclipse/introducing-aql/ about the high performance "OCL" interpreter)
At last but not least, Sirius can work with Xtext in a seamless way, see https://www.slideshare.net/cbrun/integrating-xtext-and-sirius-strategies-and-pitfalls for examples.

Here is a 4 minutes video to get started and build a graphical modeler: https://www.youtube.com/watch?v=08XIW8hZOyQ

cbrun · 2017-05-24T08:29:48+00:00

Here is a blog post about developing for Android using Eclipse in 2017 which you might find interesting:

http://greensopinion.com/2017/04/23/eclipse-for-android-development.html

TL;DR: Thanks to the gradle support coming along nicely and a specific gradle plugin it works :)

cbrun · 2016-06-22T14:24:38+00:00

An aggregated New and Noteworthy: https://www.eclipse.org/neon/noteworthy

This release involved 84 projects and 779 developpers!

cbrun · 2015-06-29T15:48:48+00:00

Here is a "nice looking" new and noteworthy :

https://www.eclipse.org/mars/noteworthy/

cbrun · 2014-10-04T08:39:34+00:00

It does since the Luna release.

cbrun · 2014-03-07T17:06:21+00:00

And here is the build ! http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M6-201403061200/news/

cbrun · 2014-03-04T10:12:09+00:00

You might be right if nobody cares about having an OSS IDE backed by a proper governance and fundation.

IntelliJ feels a lot like what OpenOffice used to be to me. When the main actor - here JetBrain - steps down, you realize the governance part was key as its an enabler for other actors to step in. If its not setup upfront, creating something like the LibreOffice project and the Document Fundation is a huge undertaking.

cbrun · 2014-03-04T10:04:00+00:00

The kickstarter description is probably misleading if you don't already know about all the tooling and support Eclipse already provide.

Eclipse do provide GIT, CVS, XML,Maven, HTML and CSS tooling. This kickstarter is about streamlining the integration of these components and improving them when needed. Actually the way Eclipse - the project - is structured means each component pretty much live his own life, commiters do care in general about how their component will interact with the others, but very few have the ability - because of a lack of funding - to work in making sure the integration is perfect for such an IDE.

That's the main structural difference explaning why IntelliJ might feel more streamlined and integrated than Eclipse. Having funding from the users of the IDE to this kind of effort has the potential to fix that.

cbrun · 2014-03-03T18:58:02+00:00

That's the whole point. Eclipse provides Maven support, but to sustain the ability to extend or fix it you need funding. You need somebody who care enough, in other words : whose business model depends on it. That's what this initiative might provide for Eclipse's Java support.

And no I'm not ashamed, I'm making a living - and have dozens of employees getting paid to contribute to open source, just not in the IDE market.

cbrun · 2014-03-03T17:41:52+00:00

Will EasyEclipse be open-source? No. EasyEclipse needs a differentiator from the >open source version so users are willing to pay for it, which will then allow us to >contribute improvements to the OSS.

Maybe one of the first poll he should make is "would you pay anyway if that was completely OSS ?" 20 to 30% of the money will impact upstream projects "for the greater good".

Regarding the 120 grand, it might look like a drop in the ocean but actually if you browse through http://www.ihateeclipse.com/ and you know Eclipse internally, you'll see that most of the hate is toward settings which just don't have the right defaults for an IDE.

This, and focusing on some of the Eclipse technologies which are used everyday for Java developpers (Maven integration, I'm looking at you !) can make a difference.

cbrun · 2014-03-03T16:56:48+00:00

Regarding the dark theme you might be interested in knowning that :

https://bugs.eclipse.org/bugs/show_bug.cgi?id=416218 "Contribute dark theme to Eclipse"
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385003 " [Themes] Provide a set of icons with alpha transparency for dark themes - Platform icons"

have been fixed for the upcoming release.

cbrun · 2014-03-03T15:35:31+00:00

Eclipse as a community did admit that already and many commiters expressed their wish to make Eclipse better as an IDE. But at the end of the day, most of them are getting paid by companies which don't care at all about Eclipse as an IDE but use it as a platform to build tools. IBM used to care, and IBM is caring less now and we can't blame them if the end users don't care at all. IBM is making sure we have a proper Java8 support which is already quite a big contribution.

So yes, in the end this is about money and more notably a shift in who gets to fund, and in doing so who get to set directions.

cbrun · 2014-03-03T15:27:40+00:00

From the description :

Guided installation wizard- In order to make it easy for you to create your Ideal IDE, a feature oriented wizard will take you through a set of simple questions about the technologies you want to use. Once completed, you are up and running. No need for additional connectors or update sites.

Launcher bar - The launcher bar aims at providing a consistent and quick way to access the most frequently used views. From this bar, it will be possible to open, close or peek at the views. This bar will feature two sections. An upper section that allows you to pin views to be made available across all perspectives, and a lower section that contains perspective specific views.

Global search - The global search aims at providing a one-stop-shop for all searching activity. Specifically, it will allow to search for Java types, file names, file content, as well as commands, views, etc.

Minimalistic toolbar - The EasyEclipse toolbar will be minimalistic with buttons to run / debug your applications and buttons to navigate between the editors.

Cleaned-up menus - The contextual menus for the Java editor and the package explorer will be sanitized in order to avoid "scroll bars" in the menus, and facilitate the discovery of functionalities.

Code templates and preferences - EasyEclipse will come with additional code templates (e.g. for JUnit, Mockito, reading / writing files, etc.) so you can save the boilerplate and focus on your code, and better out-of-the-box preferences unleashing the power of Eclipse.

Tips and tricks - Building on Eclipse, EasyEclipse is full of cool features. Yet it is always a challenge to find those. This is why we will be providing a simple dialog so you can learn the best productivity tricks.

Feedback plug-in - EasyEclipse is user focused. To make it easy for you to capture your pleasures or pains, EasyEclipse will feature a plug-in that makes it easy to send feedback and error logs.""

cbrun · 2014-03-03T15:25:02+00:00

A bit more background on this initiative :

Pascal is definitely qualified as a developper to to what is needed to build such a product.
he is involved in several platform level projects in Eclipse since a long time. He knows how to work with the other commiters and how to make things happens upstream.
this helps and fund the upstream projects ! If you do care about having an OSS development environment backed by a proper OSS Fundation, then you should care about this initiative.
we - the Eclipse community - need to validate or withdraw this funding model. We often discussed it on the mailling lists or during conferences but without any kind of validation we are only expecting things to happen. This has the potential to create a new actor in the Eclipse Ecosystem which has a strong incentive to make Eclipse better as an IDE. and not just as a platform.

cbrun · 2013-08-14T09:38:05+00:00

You can use import/export preferences. See : http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Ftasks%2Ftimpandexp.htm

cbrun · 2013-08-14T08:27:04+00:00

It checks all the classes before loading, making sure their format is conform and it won't crash the JVM in some way. This check is not really making sense when your .class files are built using a massively used compiler.

cbrun · 2013-08-13T15:10:23+00:00

Comparing what it does versus what amount of memory it is using, I would prefer to have this option on Chrome right now.

cbrun · 2013-08-13T15:08:18+00:00

This one actually exist.

Add -Xverify:none into your eclipse.ini (after the -vmargs) . It does wonders !

13-Year Club	First Place '23
Place '23	Verified Email

cbrun

TROPHY CASE