Javier Llorente
Javier Llorente
I can still reproduce this issue with NetBeans 15 and 16-rc1.
In my opinion, it's a bit complex as a logo. I would use it for a T-shirt :)
> This will brake Java EE/Jakarta EE 8 and prior projects, maybe add another Library called Jersey 3.x.y? Can we ship two Jersey versions without having conflicts?
At some point we will have to upgrade to Jersey 3. Not sure if it's the right moment to do so. As a side note, I think that the Jersey...
> You can have different versions of the same library, check the Ant Library, there are different versions for JSF and Spring: [...] >I do not think it is as...
> Ok, my take on this is: > > a) jersey is broken because it relies on autodetection of features and does not protect against classes it can't load b)...
I have created a module for Jersey 3 to avoid conflicts with Jersey 2. It is based on websvc.restlib.
I have updated the PR title and text from the first comment
RestClientTopComponent instantiates a RestClient on its constructor. That's all. I have to investigate why it's slow the first time.
I can't reproduce this with 0.5.3. I am getting different content ("es" version instead of "de").