On Tuesday 25 May 2010 2:44:39 am Aleksei Valikov wrote:
> > That said, there is a saying in Maven land:
> > Friends don't let friends use the java.net repo
> > 
> > java.net is a POORLY run repo and I would STRONGLY recommend people make
> > sure they DON'T rely on that repo for their builds.   Thus, to me, if
> > it's only deployed there, it doesn't exist.   It needs to get to
> > central.
> 
> Well, if only central was easy to upload to.

Well, it can be.   If you want to switch your projects to deploy to the 
Sonatype repo instead of java.net, then it's trivial.   See:

http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-
maven-repository-diy/

Anything projects deploy there get synced to central within hours.   Not sure 
if that would be allowed for projects at java.net, but definitely worth 
pursuing. 


> As for the other point you mention, I'm not quite sure. I not a lawyer
> so I don't see any direct advantages of APL vs. BSD-Style license I'm
> using now. I'm also not sure that anyone from Apache will be fixing
> anything in JAXB2 Basics in a timely manner.

Well, the GOAL would be to get the authors to keep contributing and become 
committers at  Apache.  :-)   

> At the same time I can expect quite a number of problems when merging
> JAXB2 Basics to CXF - or even moving it to Apache in general.
> 
> > JAXB2 Basics stuff seems to be in OK
> > shape, but the other jaxb-commons stuff is a disaster.
> 
> True. I've made a couple of efforts trying to organize jaxb2-commons
> but finally came to the conclusion that I'll have to mavenize and
> manage these projects myself - which I wasn't quite ready to do.
> Therefor I've moved my plugins to JAXB2 Basics sub-project and kept a
> bit of distance to jaxb2-commons. I've also realized that you can't
> force everyone to use Maven just because you like it.

Like I said though, JAXB2 Basics is the least of the concerns.   It's the 
"dead" plugins in jaxb-commons that really have no maintainer at all that I'm 
kind of concerned with.     At least at Apache, someone would be around to 
apply patches and do periodic releases if someone files an bug with a patch.

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

Reply via email to