As discussed on various mediums (irc, hipchat, mail)
dropping any parsers/xsd schemas included in EAP 6.0.0(AS7.1.2) and up doesn't really make any sense at this point.

It would just make migration efforts harder.

We need to make sure that all old parsers still provide working subsystem as I know some of them have had problems with that.

We could probably go and remove any parsers introduced before AS7.1.2 for example ones from 7.0.x series.

That shouldn't be a priority or standalone task, but if someone is doing work in same area it could go ahead.

If anyone sees any problems with supporting that old parsers please speak up.

--

tomaz

On Thu, Apr 2, 2015 at 6:23 PM, Brian Stansberry <brian.stansberry@redhat.com> wrote:

On 4/2/15 4:46 AM, Tomaž Cerar wrote:

On Thu, Apr 2, 2015 at 11:34 AM, Rostislav Svoboda <rsvoboda@redhat.com
<mailto:rsvoboda@redhat.com>> wrote:

Doesn't "anything that is older than AS7.3 / EAP 6.2 is optional and
can get dropped." affect https://issues.jboss.org/browse/EAP7-93 ?

No it doesn't, it is somewhat related but EAP7-93 will still be satisfied.

It's a good point though. Dropping this support has the potential to make that work harder. It doesn't make it impossible, but being able to parse old configs in the main server/HC code base might make EAP7-93 work easier.

--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat