users@jersey.java.net

[Jersey] Re: Where did the Jersey committers go?

From: Tatu Saloranta <tsaloranta_at_gmail.com>
Date: Fri, 11 Oct 2013 08:31:11 -0700

Good to know, thank you for sending quick update.

This came from my learning about project Sjsxp Stax parser that has been
folded to openjdk.
I know there are many reasons for future of various projects; and that
Sjsxp hadn't had active owner for long time. But I was afraid that this
could be reflection of larger changes: Oracle as a corporation seems to
have very different view of how to deal with open source projects.
It is also often the case that when original authors move on, changes to
project happen; especially if people are assigned based on their roles at
work over their own interests. This is the background for my (pointed)
questions.

I am happy to learn I was wrong with my guesses here. Sorry to sound like
troublemaker, but I do care about future of this project. I have built many
services on top of Jersey, so I want the project to succeed.

-+ Tatu +-



On Fri, Oct 11, 2013 at 1:07 AM, Marek Potociar
<marek.potociar_at_oracle.com>wrote:

>
> On Oct 11, 2013, at 12:27 AM, Tatu Saloranta <tsaloranta_at_gmail.com> wrote:
>
> Another question is what will happen to Open Source Jersey project: from
> other projects it seems that anything bundled by JDK are being merged into
> OpenJDK.
>
>
> This is just an illusion. There are many more projects outside JDK than
> the ones that were merged into JDK. We have no plans to merge into JDK at
> the moment. We would loose a lot of release agility if we did that.
> Currently we release every 4-5 weeks. Imagine JDK releasing that often...
>
> So will Jersey live on as separate thing, or just be piece of another
> project (Glassfish?).
>
>
> I genuinely wonder where do these questions come from? Jersey is a
> standalone project - it always was. It has a dedicated website, dedicated
> code base, dedicated issue tracker. It provides JAX-RS RI. JAX-RS is a
> standalone spec. It is also part of Java EE and as such Jersey is a core
> part of GlassFish. Jersey is also commercially available in WebLogic and
> Oracle GlassFish Server. However Jersey integrates with many other
> containers, e.g. any Servlet container (Tomcat, Jetty, ...) and natively
> with a few other containers too (Grizzly, JDK HttpServer, Simple HTTP
> Server...).
>
>
> I much prefer modular development, with steady released (release-early,
> release-often), instead of Cathedral-style big corporate pushes.
> So here's hoping that there would still be agile project for JAX-RS
> implementation; Jersey has been trailblazer in the past.
>
>
> We do not have any intention to change that approach in the foreseeable
> future. The core Jersey team is not a large one, so we may get quieter or
> slower from time to time (esp. if some bigger event distracts our focus),
> but should not be interpreted as an indication of us loosing our agile
> approach to Jersey development or releases. Obviously, the more
> contributions we can get from the community (whether it is participating in
> our mailing lists or submitting patches and new features), the better for
> Jersey.
>
> Marek
>
>
> -+ Tatu +-
>
>
>
> On Thu, Oct 10, 2013 at 2:02 PM, cowwoc <cowwoc_at_bbs.darktech.org> wrote:
>
>>
>> Out of curiosity, do any of the Jersey committers still read this
>> mailing list? I don't recall seeing you answer any post for a couple of
>> weeks now. Is everything okay?
>>
>> Gili
>>
>
>
>