On Tue, Mar 31, 2009 at 10:33 AM, Farrukh Najmi
<farrukh_at_wellfleetsoftware.com> wrote:
> Tatu Saloranta wrote:
...
> Why not just checkout the jersey source code from svn:
>
> <https://jersey.dev.java.net/source/browse/jersey/>
Yesl I was just thinking of adding a hyperlink from tutorial/FAQ there
(and with full navigation down the hierarchy to reduce number of
clicks to get there).
> and then open the corresponding project in a maven supporting IDE like
> NetBeans?
>
> That works for me. I just need to translate the URL Paul gives for a sample
> to a sample project in jersey source code.
Sure that works -- but for casual use it's still more work. :)
That is, yes, I have Jersey sources from svn myself, and can open IDE
(or just Emacs). But it's still simpler to google for "jersey sample",
then point and click.
Sort of like difference between having javadoc jars in Maven, vs.
having link to where javadocs are published. After a while it makes
sense to get a local copy, but at first it's good to have a
browser-accessible version. Esp. when evaluating whether one is
interested in project -- no sense d/l:ing something you won't use.
I am not saying this must be done, just saying that it REALLY helps
adoption & user happiness to make simple things simple.
One of those nice-to-have things.
Thanks!
-+ Tatu +-