BTW, there is a bug when you use ${basedir} inside of
<module>{$basedir}/somemodule</module>
For example, if your basedir is d:\app\module2, it expands to
d:\app\module2d:\app\module2
I'm also trying to do somewthinbg similar to you. I'm using a Java/XML
binding library (jibx) that requires it to bytecode enhance all the classes
that it touches. If the classes are across modules, then it needs all the
classpaths of the modules it needs at the same time to bytecode enhance.
It appears that the design of Maven as far as dependencies is to JAR your
artifacts and place them in your repository first before you use them in
another module. There does not seem to be a way to relatively find the base
directory for dependent modules. If I can get the basedir of the parent root
artifact, then I could use
<module>${parent.basedir}/ovr/common/servlets</module>
or such to jibx my artifact and have access to other artifacts class files.
I don't understand why this seems to be such a difficult concept and request
to understand. I hope we get an answer to how to perform multi-module
projects and have access each modules path.
Frank
