Hi, I know how it's described on sourceforge and JIRA, but I would like to relate two contrasting experiences that I've had recently.
I posed a question to the jibx-users list. As part of my question, I stated that I would try to create a test case and raise an issue in Jira if I managed to demonstrate a problem with current CVS HEAD. This hasn't proved as straightforward as I would have hoped. Another open-source project that I recently submitted something to was Castor (I've used the JDO-like stuff and had an issue with a recent release). That had a very low barrier to entry to creating a test case and submitting a patch, which is described in more detail here[1]. In particular, please note the provided templates, which make it trivial to create a test case that will slot into the existing project build. I believe Apache ANT provides a similar way to start contributing, although I haven't checked out the source of that project for a year or so. I would like to suggest that this approach gets evaluated with a view to providing something similar for JiBX. I will be able to help with this in the very near future. More immediately, I would appreciate guidance on how best to create a test case that tries to demonstrate a problem with the binding compiler. 1. I could stick it into one of the existing ANT targets, but then it would break everything due to the lack of isolation. 2. I could create a separate ANT target for this, which might provide a bit of isolation for the failure, but doesn't appear to be a good long-term solution for integrating things into the build; i.e. future contributions should just be picked up as they are created. To my mind, that would be normally served by just adding new subclasses of junit.framework.TestCase and any required resources, but that doesn't appear to be how JiBX is currently tested. 3. I could provide a separate project, with Java files, ANT build.xml, bindings, etc. Again, my issue with that approach is that it doesn't allow for easy integration into the codebase to ensure that regressions aren't introduced. So I'd like to gain a better understanding of how the project is structured before I start contributing. The only thing that I've found which talks about this is in the mailing list archives [2], but that doesn't look like anything happened with it? Cheers, James [1] http://castor.codehaus.org/how-to-submit-a-bug.html#Submitting-a-problem-report [2] http://marc.theaimsgroup.com/?l=jibx-devs&m=114973848703767&w=2 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ jibx-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-devs
