[Jboss-dev-forums] [Design of JBoss Build System] - Re: JBoss Third Party Build

[<rl...@jb...>]

I worked with this yesterday and created a build-thirdparty.xml based off of what was in the thirdparty directory in the 4.0 branch.   I found a couple of things that will need clarification.

1)  hibernate thirdparty vs. hibernate module

Currently when we try to pull down the thirdparty modules the build sees a directory "hibernate"  (our integration module).  Because this module exists it will not pull down the thirdparty component "hibernate".   How should we resolve this?   The way the build is currently structured a thirdparty component cannot have the same name as a source module.   Should the hibernate thirdparty be moved to jboss/hibernate?  

2)  what we use vs. what is there

If I go through every module under 4.0 (e.g. iiop, varia) looking at the build.xml file and look at what library classpaths are defined, and then creating a list of all library dependencies required, the list does not match the number of items in thirdparty.  I assume some items in thirdparty (the early version of tomcat for example) are no longer used.   Should I base the generated libraries.ent off of the cvs thirdparty dir as a whole, or just off of what is used.  

3)  naming conventions

Currently in the repository we have some dual directories, one called juddi, one called juddi-juddi.   Which should I base off of?

4)  new thirdparty items

In some cases, such as apache commons, the jars have been moved to their own repository locations.   Won't this necessitate a change to the build.xml files ?

Thanks!
Ruel Loehr

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882653#3882653

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882653