How do I specify a classpath for a specific Build Definition?
Existing Build Definitions and Ant script do not have classpath defined anywhere, and use the standard buildtoolkit classpath.
I would like this Build Definition to use a specific classpath, to load an alternate jar file that the standard Build Definitions should not know about. -lib in Ant Arguments doesn't seem to do anything, nor does classpath in the ant script, or in the taskdef. Should this be possible, or am I doing something wrong?
|
One answer
|
To resolve my own question, as long as the package and class names are shared between the custom jar files and the standard jar file in buildtoolkit directory, the buildtoolkit version will always be picked up. Specifying -lib or classpath will not do anything as the buildtoolkit version will take precedence. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.