On 23 May 2016 at 21:01, Owen Taylor <otaylor(a)redhat.com> wrote:
Are you talking about the JBoss suite of Eclipse plugins? If so, I think
adding Eclipse and the plugins is probably more of a size increase than we
really want to add to what we ship as part of the default image. But we
should definitely make sure that it's really smooth to get going with JBoss
Right now when I try 'dnf install eclipse-jbosstools' on Fedora 24 beta I
Error: nothing provides osgi(org.eclipse.core.runtime.compatibility)
needed by eclipse-jbosstools-common-4.2.2-1.fc22.noarch
So it looks like the packaging of these tools hasn't been updated
In fact, this package was retired because nobody stepped up to maintain it.
From my experience, in the Eclipse world, it's much more normal
plugins through the Eclipse user interface than to use packages, so that
might be the reason.
Especially when looking ahead to the Flatpak future, I wonder if packaging
Eclipse plugins makes sense at all. If we stop doing that, can we make
installing the JBoss development easier than following the instructions for
the Eclipse Marketplace on
Do we need to?
----- Original Message -----
> I've been thinking, can we have JBoss development tools by default on
> anytime soon? We've been pushing a lot of down-stream projects up on
> so why not our very own JBoss?
> desktop mailing list
desktop mailing list