Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Dec 2015 15:47:39 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 205490] java/wildfly80 : uncontrolled wildfly proliferation
Message-ID:  <bug-205490-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205490

            Bug ID: 205490
           Summary: java/wildfly80 : uncontrolled wildfly proliferation
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: marino@FreeBSD.org
                CC: yerenkow@gmail.com
                CC: yerenkow@gmail.com
             Flags: maintainer-feedback?(yerenkow@gmail.com)

According to wildfly developers:

=3D=3D=3D=3D http://lists.jboss.org/pipermail/wildfly-dev/2015-August/00437=
5.html
WildFly is a community driven project and is moving fast, WildFly 10
is going to be released on October and AFAIK there is no formal
support for a released version (ex.: 8.x) after the new version comes
out (ex.: 9.x) there will be probably a few patches or backports to an
earlier version but to stay really "supported" you must use the last
available version.

All WildFly versions (8.x, 9.x, 10.x) comply with the Java EE 7
specification, so if you stick to the standard then your app should
run without problems in a later version.

If you really need support or a formal end-of-life, then you must
acquire a JBoss EAP subscription. For the moment there is only
available JBoss EAP 6 wich comply with the Java EE 6 specification,
but JBoss EAP 7 is on the works :-)

Regards.
Jorge Sol=C3=B3rzano
=3D=3D=3D

That means without question wildfly80 and wildfly81 are the equivalent of
EOL/unsupported.

Since Wildfly90 is the current version, then conceivably wildfly82 could
receive some updates.

What is the plan for wildfly?  becuase I do not want to see every release g=
et
it's own port.=20=20

I think wildfly80 and 81 should be deprecated and removed.  As soon as
wildfly100 is released, then wildfly82 should be deprecated and removed.=20
Ideally there should only be two wildfly ports: the current and the upcomin=
g.=20
At the very most three: current, previous and upcoming.=20=20

Five is way too much IMO

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205490-13>