Here are my thoughts on the Jersey Maven release process:
1) The java.net maven repository is meant for release builds and not as a maven nightly repository for snapshot builds
2) Since Jersey is the RI for the JSR 311 API it makes sense to release both together during official project releases.
3) Users that need the latest build from the source control system can run maven locally to build and create local snapshots on their workstations. They then have the option to publicly publish that snapshot to a remote repository using the deploy-file maven plugin. I have done this myself.
4) The build.properties should reflect the latest release version and snapshot version. Whenever jersey is released in tandem with the JSR 311 API the release version and/or suffix for both should be incremented so the same version name is never released more than once.
Cheers,
Aaron
Marc Hadley <Marc.Hadley_at_Sun.COM> wrote: On Dec 6, 2007, at 5:26 AM, Paul Sandoz wrote:
>
> I am still reluctant to push out the builds of the trunk to maven
> because it may push out intermediate versions of the JAX-RS API.
> Perhaps i am being a little pedantic over this. What do others think?
>
I agree, I think it would be confusing to push out builds while we are
in the process of moving from one version of the API to another. If we
made the switch from one minor API version to the next all in one go
it wouldn't be so bad but having intermediate versions complicates
things.
Marc.
---
Marc Hadley
CTO Office, Sun Microsystems.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: users-help_at_jersey.dev.java.net
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.