Here is what I'd like to do in the next 2 weeks.
HibernateExt/annotations-commons
HibernateExt/annotations (old /metadata)
HibernateExt/entityManager (old /ejb)
HibernateExt/search
HibernateExt/validator
what is annotations-commons ? Just commons ?
Alternatively, annotations and entityManager under a jpa directory
HibernateExt/annotations-commons
HibernateExt/jpa/annotations (old /metadata)
HibernateExt/jpa/entityManager (old /ejb)
HibernateExt/search
HibernateExt/validator
Why the extra level ?
or simply get rid of HibernateExt
annotations-commons
jpa/annotations (old /metadata)
jpa/entityManager (old /ejb)
search
validator
(tools)
fine by me IFF (especially) hibernate core and the other modules
could get some shared build stuff and/or proper dependency management
so we don't repeat our self constantly in all those build files.
thoughts?
I guess your most important immediate need is to have separated
search/validator from annotations
and for that just doing the first split should be trivial since that is
what we can do today
"painlessly"
If someone knows how to physically do that with SVN without loosing all
the history, esp since we have trunk and branch_3_2 (main work
currently)... I am all ears :-)
svn copy your stuff to the correct places i assume.
PS: I thought about doing standalone distributions while keeping the
same dev structure, but Hibernate Search is getting more complex with
the master/slave mode and I need multiple src/test structures for it
same as hibernate tools I assume; why does this prevent having the same
structure ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss a division of Red Hat
[EMAIL PROTECTED]
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
