Hi Frank,
in my present projects I only needed to compile bindings for single
modules as the whole domain model usually resided in one module.
The current version of the maven2 plugin will only work module by
module. As the documentation for maven plugin developers isn't the
greatest yet I cannot really say when and if it will be possible to
run the plugin across modules in the future.
Regards,
Andreas
On 11/1/05, Frank Mena <[EMAIL PROTECTED]> wrote:
> 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}
--
Andreas Brenk
[EMAIL PROTECTED]
http://andreasbrenk.com/
HS^�隊X���'���u��jg����z�������!jY^���+a����z�'�j �������'���������y��m秵��v�0�v�ڙZ�f�������z���t��+f=#'$���ek(m������q����z��z�'�j)���o�z�&j)b�
b���o�z�%��l���q����z�m��?�X���(�� ~��zw��X������b��?�&��ǫ
