On Mon, 2015-08-24 at 15:00 +0200, Max Rydahl Andersen wrote:
Do we really need to insist java applications like WildFly and Eclipse
decomposed down to individual RPM's ?
I understand very well reasoning from both sides. Decomposing makes it
easier to track packages that need to be updated (CVE's) because the
idea is to have only one place in the system where you need to patch. On
the other hand - different projects have different schedules and
requirements, so managing all of them to use a specific version of a
specific libbrary is very hard, it's time soncuming and sometimes
impossible. This leads to frustration and to escape from the
packaging/maintining work. I'm currently in that phase.
Could it not be sufficient (and easier) to just have one big RPM for
Basically you're talking about this (I announced it some time ago in
This is still a valid RPM, but it's not built in the Fedora way.
Meaning, sure - need to find source and rebuild to check origin but
to keep coordinating dependency jar updates *unless* there is a known
for a jar included ?
just thinking out aloud.
> It's been long time since I talked to you guys. There are many reasons
> for it, but most important one is that I was pulled to do some of the
> Docker work on the Middleware side and I simply had no time :/ Even
> worse, I do not see the end.
> WildFly is in a pretty bad state now, sadly. New versions (8.2.0.Final
> and later 9.0.0.Final and of course 9.0.1.Final) are avialable since a
> while but it the package has not been updated. I did some work to make
> it happen:
> But then I was pulled back to the other work and it basically died.
> The current status is a result mostly because of lack of my time, but
> also no joy with dealing with such a fragmetized beast. The single
> distribution was split into pieces and currently the WildFly depenency
> chain contains around 200 packages, whereas I'm alone maintaing about
> 130 of them (if you want to take a look at packages I maintain:
). When I was
> working only on packaging of JBoss AS (and later WildFly) this was
> doable, but in current situation - I'm not able to maintain it
> It's really sad to see how this energy put into this effort is now
> There are currently many bugs reported against my packages (WildFly
> deps), but I just don't have time to fix them making some people
> which is of course not my intention. Gil is helpful as always sending
> some patches, but I don't even have time to look at them :( Basically
> maintaining WildFly is a full time work for one person.
> I need an advice from you guys how to proceed in a best way with this
> stuff, since I'm not closely following the Java world in Fedora
> (sorry!) maybe I'm missing some obvious solutions.
> Orphaning WildFly (and other packages) is the last thing I want to do,
> but I'll do it if we'll not find any solution.
> So, here we are, let's talk!
> java-devel mailing list