From: <ad...@jb...> - 2005-05-19 18:08:50
|
"rya...@jb..." wrote : "ad...@jb..." wrote : | | Ideally, only primary components are in the top level build during normal development. | | e.g. JBossAS contains naming, jbossmq, etc. it does not define log4j because | | that is a secondary dependency introducted by common/logging. | | (I haven't created a usecase discussion for component builds yet...) | | | | Right, but during normal development, developers are still going to need to be able to build a release image for testing. Which means there will need to be one version of log4j selected somehow. So this target is not just for calling immediately before a release. I'll talk about release issues in a separate thread, but in general developers will want to build multiple release images (for testing different configurations) and we will probably be moving to an installer based release where the user will be creating the final release image themselves. unzip jboss-4.0.4 cd jboss-4.0.4 install -config=default or install -config=all or install -config=jms or install // use a gui to create a custom config View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878427#3878427 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878427 |