From: <rya...@jb...> - 2005-04-27 21:55:00
|
I'll start with the easiest questions first :-) "tom...@jb..." wrote : I am still not totally clear on the source tags and what exactly they are defining (can these be any free form strings, or do they have to be 'main', 'test', etc.?). | These are just the names of the directories under your src directory. They have no special meaning to the build system. So if you had a src/foo directory, you could generate compile targets for it like this: <source id="foo"/> which would result in a build.foo target. "tom...@jb..." wrote : Am not sure how to specify a string expression for the files I want excluded. Yes, that's certainly a limitation. Is this an actual need at this point? If so, we could change that attribute to be an Ant patternset refid instead of the actual pattern. anonymous wrote : So now just need to be able to specify exactly the jars included on the classpath for the test run and how to pass the jvmarg parameter. I see that runtest uses pathElements for the classpath, but don't know where the values come from. | The pathElements tag is a special tag which resolves to the inputs of your source - and the jars in the Classpath of your inputs manfest. So if you have: <source id="tests"> | <input="jboss-common.jar"/> | </source> The will include jboss-common.jar in your test's classpath, as well as all of jboss-common.jar's dependencies. You can see this working by using the special show target: ant -f jbossbuild.xml show -Dshow=runtests.test This will let you will see the target that is generated, and what the actually resolves to. Also, see the bottom of this page: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=58993&postdays=0&postorder=asc&start=10 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875671#3875671 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875671 |