#1174 Exception - F20 Self Contained Change: WildFly 8 - https://fedoraproject.org/wiki/Changes/WildFly8
Closed None Opened 6 years ago by jreznik.

I'm asking for an exception for WildFly 8 Self Contained Change. It was discussed with Change owner pre-submission deadline but not submitted. It's past Change Freeze but Change is already imported to F20 and it is testable and substantially done - waiting for push (https://admin.fedoraproject.org/updates/wildfly-8.0.0-0.6.Alpha3.fc20). It's Self Contained Change with limited scope to other Changes and it could be interesting change from marketing POV/release notes and docs.

Marek, I see it's Alpha 3 - what is the timeframe for final release?


By "waiting for push" you also mean "first package for Fedora was built today" :-)

Unless I've completely misunderstood past discussions about JBoss/Wildfly, it's a platform on which other programs are written, correct? If that's the case, this should be a system wide change rather than a self-contained change as changes to this package can have a cascading effect on other, unrelated packages.

That said, repoquery finds just two things that currently depend on jboss-as in F19 and F20:

  • eclipse-jbosstools-as-0:4.1.0-2.fc19.noarch
  • ovirt-engine-0:3.1.0-1.fc19.noarch

I'd be okay with accepting this as a late system-wide change provided that the Change Owners commit to fixing breakage in other packages caused by this and implementing their contingency plan if they can't fix the other packages in time. (Note that this means they should have a contingency plan as well...)

eclipse-jbosstools are tracked by the WildFly team, actually it's needed to fix FTFBS https://bugzilla.redhat.com/show_bug.cgi?id=992169

Replying to [comment:2 toshio]:

By "waiting for push" you also mean "first package for Fedora was built today" :-)

More or less, yes :) I was on vacations :) In the next weeks I'll focus on testing and upgrading to more stable (version-wise) version.

Unless I've completely misunderstood past discussions about JBoss/Wildfly, it's a platform on which other programs are written, correct? If that's the case, this should be a system wide change rather than a self-contained change as changes to this package can have a cascading effect on other, unrelated packages.

Depends how you look at it. From one side it's an application server, just like jetty or tomcat. On the other hand it's a platform where you can run other things on top of it.

oVirt is the first application to be run on top of JBoss AS / WildFly packaged into Fedora. There can be more in the future, of course.

The eclipse-jbosstools package is a different thing. This is a set of plugins that make it easy to use JBoss' technologies (including WildFly) in Eclipse. The WildFly integration makes it possible to deploy for example to the application server your app written in Eclipse.

I'd be okay with accepting this as a late system-wide change provided that the Change Owners commit to fixing breakage in other packages caused by this and implementing their contingency plan if they can't fix the other packages in time. (Note that this means they should have a contingency plan as well...)

I'm unsure if this should be a system-wide Change, but I'm happy with either decision. I'm in contact with both: eclipse-jbosstools and ovirt package mainainers and we'll make sure everything works as expected.

ACTION: mattdm will ping Wildfly people about release notes

AGREED: WildFly 8 feature is approved (+6,-0,0)

Login to comment on this ticket.

Metadata