Hi Marek,
I am mainly concerned about the ability to run tests in parallel.
The relevant issues are:
http://java.net/jira/browse/JERSEY-705
http://java.net/jira/browse/JERSEY-710
I personally favor running each unit test against its own server
(so we need the ability to run multiple servers in parallel). The
alternative is to run multiple tests against the same server but I
dislike the idea because it makes it difficult to isolate errors.
There are also these two issues that are minor but might break
backwards compatibility:__
http://java.net/jira/browse/JERSEY-708
http://java.net/jira/browse/JERSEY-702
Thanks,
Gili
On 29/10/2012 10:14 AM, Marek Potociar wrote:
> As always, life is a matter of priorities :) We'll be trying hard to make sure the new APIs are in a good shape before release. Still, can you share your top 5 RFEs?
>
> Marek
>
> On Oct 25, 2012, at 9:23 PM, cowwoc <cowwoc_at_bbs.darktech.org> wrote:
>
>> On a related topic, I hope you keep 2.0 in beta until you're absolutely sure you want to freeze the API :) I've been a lot of RFEs in JIRA that would benefit from the flexibility of being able to change the API. Once you freeze it they will have to wait for 3.0 (which could be years away).
>>
>> Please make a full sweep over all open RFEs before deciding to freeze 2.0.
>>
>> Thanks,
>> Gili
>>
>> On 25/10/2012 3:03 PM, markecassidy_at_yahoo.com wrote:
>>> Since Jersey 2.0 is dependent on JAX-RS 2.0 finishing, does anyone have
>>> a guess as to ETA on when a production-ready release of Jersey 2.0
>>> would likely be available? Just wondering if we should stick to 1.x
>>> for systems that will be going live in 4Q 2013.
>>>
>>> Thanks for any prognostications!
>>> Mark