Re: jaxws API dependencies

[Daniel Kulp <dk...@apache.org>]

On Tue March 31 2009 3:41:40 pm hanasaki jiji wrote:
> Hmmm really good input back to the Sun folks... Any idea of how to get
> them to take notice?

Oh, we've bitched about it quite a bit already.  They know.   They just aren't 
really willing to do much about it.  Basically, each "team" is responsible for 
their own artifacts and if they feel like re-doing something, they can.   The 
non-maven projects usually are the bigger offenders.  

> Also, could the Geronimo dependencies be refactored and renamed in
> some generic manner? 

I have NO idea on that one.   We could definitely get them renamed in the 
"lib" directory.   A dependcy:copy + antrun to rename can do that.   However, 
getting them changed in the manifest jar would definitely be trickier.  Not 
sure how to do that.

Dan


> This may sound like alot of work for just naming
> sake... I have folks that get nervous when they see a JAR or other
> reference in the deployable file for their appserver of choice
> (different one) and ask.. "what the heck?  your putting the Geronimo
> appserver inside my ____ appserver?!!"



>
> Thanks.
>
> On Tue, Mar 31, 2009 at 1:32 PM, Daniel Kulp <dk...@apache.org> wrote:
> > On Tue March 31 2009 11:32:35 am nicolas de loof wrote:
> >> Hi
> >> is there any reason CXF uses geronimo specs as dependencies and not
> >> standard javax.xml ones ?
> >> They are now available in http://download.java.net/maven/2/javax/ with
> >> Apache compatible licensing AFAIK
> >
> > Other than the fact that I refuse to allow the java.net repos to be use
> > in our builds?   They have a tendency to re-release versions which are
> > incompatible and have cause CXF builds to break in the past.   Just last
> > fall, they re- released saaj-impl 1.3 which caused us issues.
> >
> > That said, I have the power to copy anything we need from there to
> > central. I do that for things like the jaxb jars and the saaj-impl jars
> > now.   However, that can lead to issues as well.   For example,
> > jaxws-api-2.1 was copied to central right after it was released:
> > http://repo2.maven.org/maven2/javax/xml/ws/jaxws-api/2.1/
> > However, Sun then re-released it at java.net.   Central has a policy of
> > not changing things.   Thus, the "2.1" jar is DIFFERENT if you get it
> > from Central or get it from java.net.    The "new" one was put in central
> > as 2.1-1 to distinguish it.   If you try CXF with the "2.1" from central,
> > it will fail. The one from Sun is OK.
> >
> > For the most part, "Apache compatible" and "Apache licensed" are two
> > different things.   If there is a "Apache LIcensed" version we can use, I
> > tend to prefer to grab that.   Plus, Geronimo, being maven people, handle
> > releases quite a lot better than the Sun folks do to avoid a lot of this.
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog