On Saturday 22 May 2010 3:51:29 pm Aleksei Valikov wrote: > Hi, > > >> By the way. Is there a way to use other JAXB2 Plugins like the 'Equals > >> plugin' or the 'HashCode plugin' > > > > Convince them to donate the code to CXF so we can publish it properly to > > Maven repos? Other than that, it's not easy. You would need to get > > the jars and deploy them locally and such. Not fun. > > I'm the author of the mentioned plugins: > > http://confluence.highsource.org/display/J2B/JAXB2+Basics+Plugins > > All my projects are Maven-based and available from public Maven repos > (like dev.java.net):
I don't believe all of the jaxb-commons plugins are available. Yours may be, but I don't think they all are. We had someone looking for the value constructor one a few months ago and wasn't found anywhere. 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. > http://confluence.highsource.org/display/J2B/Maven+Repository > > So generally there should be no problems integrating these plugin in > any Maven-project. As for CXF, here's a piece of documentation: > > http://confluence.highsource.org/display/HJ3/Integrating+Hyperjaxb3+in+buil > ds > > I'm not quite sure what you mean with "donate the code to CXF". The > project is open-source, all artifacts are available from public repos. > Is there anything else needed? Feel free to let me know (valikov at > gmx dot net) if you need any further assistance, I'll be glad to help. Anyway, the above is kind of what I was getting at. With CXF, everything would be Apache licensed, we have a good history of getting fixes out in a timely manner, and it would be automatically synced to central, not a repo that it's not recommended to use. JAXB2 Basics stuff seems to be in OK shape, but the other jaxb-commons stuff is a disaster. -- Daniel Kulp [email protected] http://dankulp.com/blog
