On Thu, Nov 20, 2008 at 6:22 AM, Stefan Bodewig [EMAIL PROTECTED] wrote:
On 2008-11-19, Jean-Louis BOUDART [EMAIL PROTECTED] wrote:
I just have two questions :
I knew I didn't reproduce all of EasyAnt's patch 8-)
- Does prefix of import / include make sense on target-group? Or
On 2008-11-19, Stefan Bodewig [EMAIL PROTECTED] wrote:
Maybe this should be a comma-separeted list of traget-groups to add
to instead.
[Maybe I should proof-read my mails before I hit C-c C-c.]
The target-group attribute now accepts a comma-separated list in svn
revision 719198.
Stefan
2008/11/20 Stefan Bodewig [EMAIL PROTECTED]:
On 2008-11-19, Gilles Scokart [EMAIL PROTECTED] wrote:
I was thus thinking to provide this classpath using the
project.setCoreLoader. But that didn't worked.
Indeed, the coreLoader is not used when declaring antlib.
Is coreLoader used at all?
I think if you want to show nice dynamic help, with rich (understand
specific) logic to select what to display, you should probably use an
help module in EasyAnt, (I mean an imported help build file exposing
an help target ot target-group).
Gilles
2008/11/20 Xavier Hanin [EMAIL PROTECTED]:
On
2008/11/19 Bruce Atherton [EMAIL PROTECTED]:
I think that summary does the job nicely. The only other topic I saw brought
up on this thread was whether a target-group should be allowed to have tasks
in it rather than requiring it to be empty. This can also be discussed
separately, though, if
I agree with Xavier a target-group is something at a higher level than a
target.
I think that the key feature of target-group is dependency injection but as
Xavier says if thread-group is the only way to have target dependency
injection, then people may use it only for that, and complain about
On 2008-11-20, Dominique Devienne [EMAIL PROTECTED] wrote:
On Wed, Nov 19, 2008 at 11:19 PM, Stefan Bodewig [EMAIL PROTECTED] wrote:
On 2008-11-19, Bruce Atherton [EMAIL PROTECTED] wrote:
The only other topic I saw brought up on this thread was whether a
target-group should be allowed to
On 2008-11-20, Gilles Scokart [EMAIL PROTECTED] wrote:
There is 2 other topics :
- What about the build events?
As long as target-groups are not different from targets from the
perspective of the person who runs ant, not the person who writes the
build file, I don't see why.
- What about the
On 2008-11-20, Xavier Hanin [EMAIL PROTECTED] wrote:
I'm not sure if it's directly related to thread-group, or to the usage made
of thread-group in EasyAnt:
could you please explain what a thread-group in EasyAnt is/does?
Thanks
Stefan
I think this is a typo he wanted to say target-group IMHO :p
2008/11/20 Stefan Bodewig [EMAIL PROTECTED]
On 2008-11-20, Xavier Hanin [EMAIL PROTECTED] wrote:
I'm not sure if it's directly related to thread-group, or to the usage
made
of thread-group in EasyAnt:
could you please explain
On Wed, Nov 19, 2008 at 11:19 PM, Stefan Bodewig [EMAIL PROTECTED] wrote:
On 2008-11-19, Bruce Atherton [EMAIL PROTECTED] wrote:
The only other topic I saw brought up on this thread was whether a
target-group should be allowed to have tasks in it rather than
requiring it to be empty.
If we
On 2008-11-20, Jean-Louis BOUDART [EMAIL PROTECTED] wrote:
The fact is target-group is not only a way to have dependency management,
but a new way to think your build-script.
Yes, but only for the person who writes the build file, not the one
who uses it. -projecthelp is for the user.
I
On 2008-11-19, 向雅 [EMAIL PROTECTED] wrote:
after patch ProjectHelper with a method accept(buildFile), if file
is xml, ONProjectHelper not accept, so all control transfer to ant
with xml. else if file is on, ONProjectHelper do it.
This change to ProjectHelper sounds pretty innocent (an accept
On Thu, Nov 20, 2008 at 9:32 AM, Stefan Bodewig [EMAIL PROTECTED] wrote:
target name=a/
target name=b target-group=a/
[OT] I recently was thinking that target ... target-group=... / is heavy.
I think using target ... group=... / is just as expressive.
The *only* differences between target
On 2008-11-20, Dominique Devienne [EMAIL PROTECTED] wrote:
On Thu, Nov 20, 2008 at 9:32 AM, Stefan Bodewig [EMAIL PROTECTED] wrote:
The *only* differences between target and target-group in trunk
are:
* target-groups must be empty
I like that.
* you cannot use the target-group attribute
On Thu, Nov 20, 2008 at 10:21 AM, Stefan Bodewig [EMAIL PROTECTED] wrote:
target-group is-a target. A plain target is a target as opposed to
a target-group.
Since I have conceptualized them in my head as something different
than targets, I forget that implementation-wise they remain targets. I
2008/11/20 Stefan Bodewig [EMAIL PROTECTED]:
On 2008-11-20, Gilles Scokart [EMAIL PROTECTED] wrote:
There is 2 other topics :
- What about the build events?
As long as target-groups are not different from targets from the
perspective of the person who runs ant, not the person who writes the
The fact is target-group is not only a way to have dependency management,
but a new way to think your build-script.
Yes, but only for the person who writes the build file, not the one
who uses it. -projecthelp is for the user.
I guess for us target-group is useful to make build modules
18 matches
Mail list logo
