I have a rather complex build. There is a top level build.xml and there are many sub projects, each having its own build.xml.
When I want to instrument the build, I only want to make changes in the top build.xml, but the sub-projects should also get instrumented.
However, when i try to instrument the code, it only instruments the code which is part of top level build.xml and not the sub-projects code, as they are in different build.xml. I don't want to set the inheritAll= true, as each projects has over-ridden the parameters.
What is the parameter I need to pass to the sub-project's build.xml in order to instrument.
Thanks for your help in advance.
If I understand correctly your question:
Simpler approach: Use a properties file in your root directory and load it in each build.xml. In this way, you only modify in one place (your properties file) and you will keep build without inheritAll. Of course, each sub-project should know to instrument the build based on the values you have in your properties file.
Normally, I would extract the common parts of the build in one single ant file to be included and executed by all the others.
What I need is when I just run from top-level xml saying with.clover <target> which would compile all the top level files as well as sub-project files. I cannot enforce the sub-project leve guys to write some targets. The only xml accessible to me is the top level build.xml.
I don't why, when I change inheritAll to true, the subproject files are getting instrumented.
But when it is false, I can't do that.
So I was wondering is there some property which needs to be set to get instrumentation of sub-projects.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot