| "Overriding previous definition of reference " ... should I worry? | "Overriding previous definition of reference " ... should I worry? 2007-06-28 - By Jay Dickon Glanville
Thanks Jurgen.
If I can ask you, and the rest of the community, for a touch more clarification.
In my example,
01] <project basedir="." default="compile" name="example">
02] <patternset id="depender">
03] <patternset refid="dependee" />
04] </patternset>
05] <patternset id="dependee">
06] </patternset>
07] <target name="compile" >
08] <echo>doing nothing</echo>
09] </target>
10] </project>
Line 03, the reference to another patternset (one that hasn't been
declared yet) in essence creates it. It's initial value is probably
an empty set.
Later on, on line 05 (where the patternset officially gets declared)
the patternset gets modified with whatever the decoration gives it.
So, as long as all my patternset declarations are grouped together at
the top of my build file, and there are no targets interspersed,
everything should be fine for me.
Is my interpretation correct?
Thanks again.
JDG
On 6/28/07, Knuplesch, J?rgen <Juergen.Knuplesch@(protected)> wrote:
> Hello,
>
> You are able to change values of patternsets ids etc.
> You are in general not able to change properties (immutability).
>
> The warning means: If you dont want to change the value of this id, then you
are in trouble.
> But if this is exactly want you want, then everythings fine.
>
> Greetings
>
> --
> J?rgen Knuplesch www.icongmbh.de
> icon Systemhaus GmbH Tel. +49 711 806098-275
> Sophienstra?e 40
> D-70178 Stuttgart Fax. +49 711 806098-299
>
> Gesch?ftsf?hrer: Uwe Seltmann
> HRB Stuttgart 17655
> USt-IdNr.: DE 811944121
> -----Urspr?ngliche Nachricht-----
> Von: Jay Dickon Glanville [mailto:dickon.glanville@(protected)]
> Gesendet: Donnerstag, 28. Juni 2007 17:46
> An: Ant User
> Betreff: "Overriding previous definition of reference" ... should I worry?
>
> Hello all.
>
> I have a build file with a set of patternsets that are declared in
alphabetical order. There are some references between then (eg: A references B
, but A is declared first).
>
> Because of these dependencies and their order, I'm getting warning messages
from ant, things like:
> Overriding previous definition of reference to dependee Should I be worried?
>
>
> As an example, I have a build file where the referrer is declared before it's
dependency is declared:
> <project basedir="." default="compile" name="example">
> <patternset id="depender">
> <patternset refid="dependee" />
> </patternset>
> <patternset id="dependee">
> </patternset>
> <target name="compile" >
> <echo>doing nothing</echo>
> </target>
> </project>
> This produces the following output:
> Overriding previous definition of reference to dependee
>
> compile:
> [echo] doing nothing
>
> BUILD SUCCESSFUL
> Total time: 1 second
>
> Should I be concerned with this override?
>
>
> Thanks
>
> JDG
>
>
> --
> Jay Dickon Glanville
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected) For additional
commands, e-mail: user-help@(protected)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>
--
Jay Dickon Glanville
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
 |
