Re: JSR311: RE: Publish jsr311-api.jar into a public maven repository?

From: Ryan J. McDonough <>
Date: Fri, 12 Oct 2007 08:26:47 -0400

I have defined the following repository in my pom.xml:


I am using this dependecy:


So far, all is working fine.


On Oct 12, 2007, at 6:01 AM, Liu, Jervis wrote:

> Hi I noticed that we've recently added jsr311-api.jar into a local
> repo in svn (trunk\repo\\jars). I wonder whether or not
> the same jar is now available somewhere in a public maven repository?
> Thanks,
> Jervis
>> -----Original Message-----
>> From: Marc.Hadley_at_Sun.COM [mailto:Marc.Hadley_at_Sun.COM]
>> Sent: 2007?9?17? 23:45
>> To: Liu, Jervis
>> Cc:
>> Subject: Re: Publish jsr311-api.jar into a public maven repository?
>> On Sep 16, 2007, at 10:45 PM, Liu, Jervis wrote:
>>> We are interested in implementing JSR-311 in Apache CXF. I've been
>>> playing with some prototype implementation codes for a few days on
>>> my own svn branch, so far so good.
>> That's great news, we'd welcome a second independent implementation
>> or we'd be happy to combine efforts via Jersey (http://
>> if that makes sense. Please bear in mind that
>> the API is a moving target and changes are inevitable, more
>> on how we
>> intend to manage this below.
>>> However the biggest problem that preventing me and other CXF
>>> developers from working on CXF JSR-311 implementation is
>> the jsr311-
>>> api.jar. No work related to JSR-311 implementation can be checked
>>> in into CXF's main trunk until jsr311-api.jar is available
>>> somewhere in a public maven repository. I wonder would it be
>>> possible to start publishing jsr311-api.jar into a public maven
>>> repository now so that everyone else who is also interested in
>>> implementing JSR-311 can move forward? Thanks.
>> We're actually already working on this as part of the process of
>> maven-enabling Jersey. We'll hopefully have something working soon
>> and I'll notify this list when the jars are published. The approach
>> we are planning to take is to publish a new jar in a maven
>> repository
>> for each stable release of the API, e.g. 0.2, 0.3 etc rather than
>> publish a new version of the jar every time we make a change to the
>> API. That way implementations can target a stable version of the API
>> and move between versions in coarse steps rather than facing
>> death by
>> a thousand changes. Hopefully this approach will work for Apache CXF
>> too ?
>> Thanks,
>> Marc.
>> ---
>> Marc Hadley <marc.hadley at>
>> CTO Office, Sun Microsystems.
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
> Ireland
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail: