Thanks,
I didn't see that other thread, but just looked it over and it does seem
to be a good way to go about it.
In the meantime, I'll also dig into the executor for our own personal
1.7 approach.
Thanks again for the comments/suggestions.
- Jonathan
Dominique Devienne wrote:
On Tue, Jul 1, 2008 at 12:41 PM, jonathan doklovic
<[EMAIL PROTECTED]> wrote:
I was wondering if anyone else thought being able to specify wildcards in
the depends attribute of the target would be helpful.
Where I work, we use a lot of build fragments that get imported, and we
would like the ability to allow the developer to add/remove build
funtionality easilt without disrupting the basic workflow.
essentially something like:
build.xml imports base-java.xml and java-checkstyle.xml
base-java.xml:
<target name="pre-compile" depends="java-pre-plugin*,compile" />
java-checkstyle.xml
<target name="java-pre-plugin-checkstyle"> ... run checkstyle ... </target>
This way a developer can add/remove something like checkstyle simply by
adding/removing the import.
This would also allow the developer to use a different syntax checker simply
by the import.
Your syntax is not backward compatible in general, but as Matt writes
a custom Executor may enable it specifically for you.
BTW your use case would be answered by a proposed extension using new
'before/after' attributes on <target> which was discussed at length a
few weeks back. Injecting dependencies that way, a la Maven, would
make plugging in things together more easily, and mesh well with
<import>. You may have a better chance with before/after than
depends="foo*". --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
