From: <rya...@jb...> - 2005-04-27 22:15:19
|
anonymous wrote : | I guess the jvmarg can be added to the runtest taskdef as well, but am not sure how to make it conditional depending of if there is a variable defined for it within the jbossbuild.xml. | Usually, you can add an attribute to an element like this, and then do conditional processing based on the presence of that attribute. However, in this case we have an optional parameter (your jvm arguments), which the template processing can't handle. I think we will need to extend the template language to allow you to do something like this: <source id="test" tests="*TestCase.java"> | <input id="main"/> | <jvmarg value="-Dloader.path=${output.lib.dir}/jboss-remoting-loading-test.jar"/> | </source> and then in our tasks.xml where we make the JUnit call we could have: <junit ... | <pathelements> | <jvmargs/> | </junit> And the above would expand to include all the jmvarg elements you defined. This would be a generic mechanism for any kind of element. Adrian? Do you see any problem with having dynamic elements like this? I haven't investigated deeply, but ant's DynamicElement seems like it might fit the bill. We need to focus on getting the build complete, but I will add this as an enhancement in JIRA if Adrian agrees. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875675#3875675 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875675 |