On Wed September 30 2009 4:06:43 am Christian Schneider wrote: > Hi all, > > there is a thread in the user list about the cxf-common-xsd plugin. > There is also the maven jaxb plugin: > https://jaxb.dev.java.net/jaxb-maven2-plugin/ > > Does anyone know what the differences are? Which plugin should we advise > to use?
Well, I PERSONALLY would recommend the CXF one for a couple reasons: 1) It's available at central. You don't need to configure java.net repo to get it. I HIGHLY advise people to NOT configure in java.net whenever possible. Having java.net repo configured in is a recipe for disaster. 2) It uses newer versions of JAXB. This is one of the main reasons we wrote our own. We KNOW we are using the version of JAXB that we test with for all of CXF. One difference is that there is a "delete dirs" to post delete some schemas that you didn't really want generated. (like stuff that is generated in multiple places) Ideally, you would use a binding file to turn off generation of the stuff to begin with, but that requires binding files to maintain and such. The cxf version also allows specifying dependent files (like files that the xsd imports) that if they change, the plugin will re-run the xjc. Nothing major. > The jaxb-maven2-plugin is not on ibilio. Does anyone know why? They say > they plan to add it since ages. Mostly cause the Sun folks are incapable of running a decent maven repository. Thus, central refuses to sync from them automatically so anything synced over has to be done manually, which obviously means it doesn't get done. :-) Seriously, anything CXF needs, I do sync over manually (I have the power!). Thus, we don't need java.net in our builds anymore. That's important. We did have java.net in our poms for a while and they managed to break our builds on three separate occasions by re-releasing artifacts with the same version numbers that really were not compatible. Using a three strike rule, the third time it happened, I removed them. I know the artifacts at central don't change. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
