Hi, >> 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.
I was only speaking of the mentioned plugins, which are a part of JAXB2 Basics. > 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. >> 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. Deploying to the central repo is surely worth considering. I'll check if it is doable in an automatic manner (I will definitely NOT be creating JIRA issues, posting bundles and so on manually - I don't have time for this). 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. 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. Bye. /lexi
