Yeah. The thirdparty directory structure under HEAD is [lib_name]-[lib_name]/[lib_name].jar. However, the 3.2 branch has a thirdparty directory structure of [lib_name]/[lib_name]/[lib_name].jar.

So have to change the buildmagic stuff to point to different directories depending on the branch (HEAD vs Branch_3_2). Is this causing a problem?

-Tom

Scott M Stark wrote:

You cannot use jboss-head with a branch tag as the module alias jboss-head is
tied to the HEAD structure through the CVSROOT/modules definition.


xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx



------------------------------------------------------------------------
*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Thomas Diesler
*Sent:* Monday, January 12, 2004 5:44 AM
*To:* Tom Elrod
*Cc:* [EMAIL PROTECTED]
*Subject:* [JBoss-dev] Build Branch_3_2


Tom,
in CVS jboss-head Branch_3_2 /tools/etc/buildmagic/libraries.ent I find
<!-- Dom4j -->
<property name="dom4j.dom4j.root" value="${project.thirdparty}/dom4j/dom4j"/>
<property name="dom4j.dom4j.lib" value="${dom4j.dom4j.root}/lib"/>
<path id="dom4j.dom4j.classpath">
<pathelement path="${dom4j.dom4j.lib}/dom4j.jar"/>
</path>
However, dom4j lives in ${project.thirdparty}/dom4j-dom4j.
What's the story here, do you know?
Cheers
-Thomas



------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to