Paul Sandoz wrote:
>
> On timely related matters we have just had a request to make the
> jsr311-api.jar available on Maven so that developers can start
> implementing. I don't know if it is an issue for other developers or
> not that jsr311-api.jar will be distributed with jersey.jar to the
> maven repository. I tend to look at it as a good thing because the API
> and RI are kept in sync, thus a developer could compare their
> implementation with the RI to see if it is doing the same thing.
Great! This might be redundant information, but: ideally it should have
a group id of javax.ws.rs, an artifact id of jsr311 and a version of
1.0-[DRAFT NAME]. Or if the jar is changing between the draft release,
it should be called a 1.0-SNAPSHOT per maven conventions. Any jar that
does not end with -SNAPSHOT is considered a final release in maven and
isn't supposed to change. This way developers are conscious that they
are depending on a changing version and they can depend on draft
releases for alphas/betas which won't change.
Regards,
- Dan
--
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog