I thought I had fixed the javaee api issue by replacing its usage
everywhere in Wildfly with the relevant individual EE module.
It looks like a few static modules still depend on it but that should
not affect deployments.
Stuart
On Fri, Feb 7, 2014 at 11:14 PM, Bill Burke <bburke(a)redhat.com
<mailto:bburke@redhat.com>> wrote:
Chris sent me this rant on overriding built in Resteasy. I replied how
to fix it on his blog. The biggest problem is javaee.api which sucks in
every EE API. Is there a reason you don't trust the subsystems to suck
in the EE APIs they need?
-------- Original Message --------
Subject: dzone rant on resteasy/modules
Date: Fri, 07 Feb 2014 13:49:02 -0500
From: Chris Bredesen <cbredesen(a)redhat.com
<mailto:cbredesen@redhat.com>>
To: Bill Burke <bburke(a)redhat.com <mailto:bburke@redhat.com>>
Just saw this by accident, have fun!
http://java.dzone.com/articles/jboss-modules-suck-it%E2%80%99s
-CB
--
Chris Bredesen
Supervisor, Software Engineering
Red Hat Global Support Services
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev