Weinan Li / JBoss
On May 10, 2016, at 5:51 PM, Rostislav Svoboda
How much work will have to be done in RESTEasy codebase ?
RESTEasy side is done:
From my perspective new features shouldn't be introduced in micro
release. If this will be about changes in WF and WF-CORE codebase to expose existing
++ some bug fixes in resteasy-wadl
It will be included into each RESTEasy release, and then for Wildfly side it will be
upgrade resteasy task.
related to integration it's completely fine to do it in micro
Nice to know :-)
What's the priority of this task versus planned project cleanup / reorganization ?
No priority is assigned. There is an issue with 134 votes:
After I added the module I closed this one and asked users to create independent bug
reports for the module.
I can work on this when no other higher priority tasks assigned to me :-)
----- Original Message -----
> Thanks for the info Tomaz :-)
> In before we just add a module directory into WildFly(update modules, add
> dependencies, etc).
> Are there any documents that describe the workflow to create feature pack?
> Weinan Li / JBoss
>> On May 10, 2016, at 12:32 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
>> I would start by creating feature-pack in resteasy
>> than add instructions how to build wildfly with this extra feature pack.
>> Once all this works fine, I would opt for adding it to WildFly.
>> but not just directly go for inclusion in WildFly / EAP
>> On Mon, May 9, 2016 at 5:12 PM, Weinan Li <weli(a)redhat.com> wrote:
>> I start to get resteasy-wadl related issues from community users, and I
>> guess it's good time to add it into WildFly. I'll work on this.
>> - Weinan Li
>> resteasy-dev mailing list
> resteasy-dev mailing list