[JENKINS-15886] parameterized builds start default ant target in Ant-Task

Hi,

any parameterized build that has an ant builder only starts the default ant target and completely ignores the given target in the ant builder options.

So if we have a parameterized build that has to use ant builders we are forced to use the default target or remove the parameter option.

---
Originally reported by seppstreich, imported from: parameterized builds start default ant target in Ant-Task

• assignee: cjo9900
  
• status: In Progress
  
• priority: Critical
  
• component(s): ant-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 20251216-182730
  

Raw content of original issue

Hi,


any parameterized build that has an ant builder only starts the default ant target and completely ignores the given target in the ant builder options.


So if we have a parameterized build that has to use ant builders we are forced to use the default target or remove the parameter option.

environment

```
Windows Server 2008 R2

Ant 1.8.3

Jenkins 1.491
```

4 attachments

- [build.xml](https://issues.jenkins.io/secure/attachment/22918/build.xml)
- [config.xml](https://issues.jenkins.io/secure/attachment/22917/config.xml)
- [screenshot-1.jpg](https://issues.jenkins.io/secure/attachment/22898/screenshot-1.jpg)
> 
- [screenshot-2.jpg](https://issues.jenkins.io/secure/attachment/22899/screenshot-2.jpg)
> 

Reproduce the parameterized Ant build using the attached build.xml and config.xml with the stated Jenkins 1.491 and Ant 1.8.3 environment. Trace the Ant builder configuration and verify that the selected target, rather than only the default target, is used; done means parameterized builds honor the configured target.

Written by the indexing model from the issue text.