Bug 37127 - The Apt task needs a way to reference options declared externally
Summary: The Apt task needs a way to reference options declared externally
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.7.0
Hardware: Other other
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Ant Notifications List
Depends on:
Reported: 2005-10-17 20:45 UTC by Konstantin Komissarchik
Modified: 2008-02-22 12:18 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Komissarchik 2005-10-17 20:45:59 UTC
We have been using the alpha Apt task quite successfully in our build scripts. 
Thanks for including it in this release!

One thing that we have ran into is that it is not possible to define the 
options externally and then reference them in the apt task (something akin to 
path refs). We are basically trying to create a fully parameterizable build 
script that includes an Apt task.
Comment 1 Steve Loughran 2005-10-17 20:56:02 UTC
Does <presetdef> or <macro> let you wrap up a new declaration with your
preferred options?
Comment 2 Matt Benson 2005-10-17 20:57:43 UTC
I concur; you should have success referencing an externally defined 
<presetdef> via either <import> or an antlib.
Comment 3 Konstantin Komissarchik 2005-10-17 21:11:44 UTC
I don't believe using macro or presetdef facility fits the bill for what I am 
trying to do. The usecase is almost identical to the path ref usecase. In 
particular, we want create a common build script that would get called from 
different places with different annotation processors. Depending on which 
annotation processors are in the processor path, the set of options needs to 
vary. So I want to allow the caller to define a named processor path (possible 
right now) and a named option set (not possible right now) and then refer to 
both when calling the Apt task.