> It might be good to run through the common dev scenarios in 
> detail to  
> see which model would work best for this project, since there are so  
> many sub-projects.

Good point. I think that we should move to a model where we have a project
that assembles a single unified jar (including merging contents of META-INF
files). This seems much more conducive to most normal uses of OpenJPA; I
think that the sub-projects should be there for advanced users and as an
internal artifact of how the product is designed and built.

Does anyone know of existing mvn technology to merge resource files? To
easily assemble jars together?

Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to