I'm +1 for this solution
2008/11/26 Dominique Devienne [EMAIL PROTECTED]
On Wed, Nov 26, 2008 at 2:06 PM, Bruce Atherton [EMAIL PROTECTED]
wrote:
Or you could just live with the verbosity of the target list, like I did,
and use naming conventions in EasyAnt. I'm sure there are many other
Any news on this point?
2008/11/24 Xavier Hanin [EMAIL PROTECTED]
On Fri, Nov 21, 2008 at 12:26 AM, Jean-Louis BOUDART
[EMAIL PROTECTED] wrote:
In addition, as we use target-group to have more genericity we
doesn't
want to have prefix on those generic targets.
I'm afraid I
On 2008-11-28, Jean-Louis BOUDART [EMAIL PROTECTED] wrote:
Any news on this point?
I've still not seen any argument that convinced me that the naming
rules for include should be different, but that's just me.
On the target-group as composite side, I may start to understand it,
but feel that
I was asking to myself the same question : why only 2 levels?
I think you are right, we don't need different type of targets, what
we should have is a new type of relationship between targets : the
PartOf relationship that allow to plug a 'lower' level target INTO an
other target.
But for the
Right. I see a part-of relationship of arbitrary depth as being best
implemented using a Composite design pattern. A target-group is a
composite for targets but is itself also a target.
The level idea was only an example off the top of my head, but in
thinking about it you are right that
On Wed, Nov 26, 2008 at 2:06 PM, Bruce Atherton [EMAIL PROTECTED] wrote:
Or you could just live with the verbosity of the target list, like I did,
and use naming conventions in EasyAnt. I'm sure there are many other ways to
address the issue.
One possible way would be to provide an
I am in the same boat as Stefan. I also don't understand yet why
target-groups are not just targets to the person running Ant.
What you appear to be arguing here is that there should be two levels to
Ant targets. But why just two? Why not three or four or five?
I've written build systems
On Fri, Nov 21, 2008 at 12:26 AM, Jean-Louis BOUDART
[EMAIL PROTECTED] wrote:
In addition, as we use target-group to have more genericity we
doesn't
want to have prefix on those generic targets.
I'm afraid I don't understand this.
One of your selling points for include was that
In addition, as we use target-group to have more genericity we
doesn't
want to have prefix on those generic targets.
I'm afraid I don't understand this.
One of your selling points for include was that the
included build is
self-contained and remains that way by prefixing all
On 2008-11-21, Jean-Louis BOUDART [EMAIL PROTECTED] wrote:
Suppose you have a build with 10 target-group which represent 10 different
generic step of your build process (like compile / package/ test/ etc...)
Then I'd consider this to be the public API and import it.
And behind you have 30
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
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
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, 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 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
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
Hi all,
svn revision 718943 contains target-group (without documentation) as a
special kind of target that must always be empty.
targets and target-groups have a new attribute target-group that can
be used to add the target(-group) to a named target-group that must
have been defined already[1].
svn revision 718943 contains target-group (without documentation) as a
special kind of target that must always be empty.
targets and target-groups have a new attribute target-group that can
be used to add the target(-group) to a named target-group that must
have been defined already[1].
Hum little mistake in my explanation :
By typing ant -p
1) Case of target and target-group mixed project help will display something
like :*Available target :*
compile -- compile the current projet
org.apache.ant#jar.compile-java -- compile java classes on the current
project
package -- package
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
should we consider target-group as an abstract target that is never
prefixed?
22 matches
Mail list logo
