I am trying to figure out how to use jibx and maven 2.  I was hoping I could ask the question here because it is hard to explain how to use jibx across modules in the maven mailing list.
 
 As an example, I have the following directory structure:

common
  common1
  common2
  subcommon
    subcommon1
    subcommon2
project1
  some1model1
  some1model2
  war
  ear
project2
  some2model1
  some2model2
  war
  ear

With the above as an example, I build 2 different projects, each with it's own ear.  They both share modules from the "common" subtree.  Each project has it's own jibx build files that span multiple modules, including some in the common tree.

When I run the jibx task post-compile, it needs to have all the classes it is going to bind in the classpath.  For a given project, some of these classes are are in the projects modules and some of them are in the common submodules.

jibx need to be run before the modules are jar'ed into the repository.  Is there a way to do this?  I was trying to create ${basedir} for the parent pom (Would be nice to have ${parent.pom.basedir}
 
- Frank
 

Reply via email to