diff options
Diffstat (limited to 'testautomation/extensions/optional/input/extension_sources/TaskPaneComponent/build.xml')
-rwxr-xr-x | testautomation/extensions/optional/input/extension_sources/TaskPaneComponent/build.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/testautomation/extensions/optional/input/extension_sources/TaskPaneComponent/build.xml b/testautomation/extensions/optional/input/extension_sources/TaskPaneComponent/build.xml index 4428a95f551b..59791c0509d2 100755 --- a/testautomation/extensions/optional/input/extension_sources/TaskPaneComponent/build.xml +++ b/testautomation/extensions/optional/input/extension_sources/TaskPaneComponent/build.xml @@ -7,9 +7,9 @@ <import file="nbproject/build-uno-impl.xml"/> <!-- - There exist several targets which are by default empty and which can be - used for execution of your tasks. These targets are usually executed - before and after some main targets. They are: + There exist several targets which are by default empty and which can be + used for execution of your tasks. These targets are usually executed + before and after some main targets. They are: -pre-init: called before initialization of project properties -post-init: called after initialization of project properties @@ -37,12 +37,12 @@ </obfuscate> </target> - For list of available properties check the imported - nbproject/build-impl.xml file. + For list of available properties check the imported + nbproject/build-impl.xml file. Another way to customize the build is by overriding existing main targets. - The targets of interest are: + The targets of interest are: -init-macrodef-javac: defines macro for javac compilation -init-macrodef-junit: defines macro for junit execution @@ -50,7 +50,7 @@ -init-macrodef-java: defines macro for class execution -do-jar-with-manifest: JAR building (if you are using a manifest) -do-jar-without-manifest: JAR building (if you are not using a manifest) - run: execution of project + run: execution of project -javadoc-build: Javadoc generation test-report: JUnit report generation @@ -62,10 +62,10 @@ </exec> </target> - Notice that the overridden target depends on the jar target and not only on - the compile target as the regular run target does. Again, for a list of available + Notice that the overridden target depends on the jar target and not only on + the compile target as the regular run target does. Again, for a list of available properties which you can use, check the target you are overriding in the - nbproject/build-impl.xml file. + nbproject/build-impl.xml file. --> |