As for the how, I can ask Damon; he has previously mentioned that he had a script to automate layout changes within a repo.
Since you are talking about a lot of moves as it is, this might also be a good time to move to the proposed directory layout where each project is its own top-level repo directory. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Friday, January 12, 2007 6:45 PM To: hibernate Subject: [hibernate-dev] HibernateExt/metadata split 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 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 or simply get rid of HibernateExt annotations-commons jpa/annotations (old /metadata) jpa/entityManager (old /ejb) search validator (tools) thoughts? 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 :-) 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 _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
