Thank you so much for including these examples. It makes all the difference in trying to understand your question.
Remember, JiBX is such an elegant solution for XML binding because there are no messy extra classes or generated source code. JiBX actually changes the bytecode of your class so it can generate XML. This means that JiBX is run right after compilation and before (jar) packaging.
Typically, maven does the following in a JiBX binding project:
1. Compiles your source code into class files.
2. JiBX modifies the class files (bytecode) so they can generate the XML defined by your binding definition.
3. Packages the class files into a jar, etc.
In your example, just move the source files from the dsk-model project to the dsk-binding project, and JiBX runs flawlessly.
I can't think of a situation where you would want to do the binding in a different project than the source files since you would be changing the class files in another project.
Does this make sense?