So far so good! Just wondering, is this the 'right' way to solve this, or should there be some versioning magic intended for this kind of scenarios. secure (Deprecated)Build ICU4J API and test classes for running the ICU4J test suite with Java security manager. What defines which of them will be used by the runner?ĭisabling the JetBrains-bundled ant seems to solve this - then runner is using ant that I bundled. Now I have two ants - the one bundled by JetBrains, and the one bundled by me. 'Apache Ant runner support' plugin's - which AFAIK represents Ant in the 'Runner type' dropdown list in build step configuration - agent side depends on 'ant' tool, i.e. The name of the plugin is then available as a configuration parameter for use in build configurations didn't magically happen. Search for jobs related to Configuration compile is obsolete and has been replaced with implementation and api firebase or hire on the worlds largest freelancing marketplace with 22m+ jobs. Steps I performed: - I repackaged apache-ant-1.8.2 so that it includes a folder named apache-ant (instead of. This is the spec file I am going to attempt to build to create the required ant package, as resulting from the merge described in the previous comment. The deployment itself can be performed with Apache Ivy or the Aether Ant tasks. Attached file ant1.8.4CentOSmoz.spec (obsolete) Details. I don't yet understand what I should do with that vs. Apache Ant provides tasks for creating the components required.

Zip it, 'Upload plugin zip', and it gets into 'External plugins' list beautifully.īut. Following that, repackaging Ant 1.10 was trivial, just modify Apache Ant 1.10.5 distribution by copying structure and teamcity-plugin.xmls (modified a bit) from TeamCity's bundled Ant distribution.

Apache ant obsolete