Re: DO NOT REPLY [Bug 49659] [regression] Project.getReference(key) no longer returns certain references

Antoine Levy-Lambert wrote on 2010/12/15 10:59:35 AM: > > My guess is that in ant 1.8.x it is only legal to use references which > have already been defined at execution time. > > So the eclipse integration would need to execute the build to find which > references are legally

Re: DO NOT REPLY [Bug 49659] [regression] Project.getReference(key) no longer returns certain references

Moving this discussion to ant-dev. My guess is that in ant 1.8.x it is only legal to use references which have already been defined at execution time. So the eclipse integration would need to execute the build to find which references are legally usable in a given target. Maybe the eclipse

Re: inherit references features for antunit?

On 2010-04-22, Jason Trump wrote: > I opened a bugzilla entry and attached a patch to it: > https://issues.apache.org/bugzilla/show_bug.cgi?id=49168 Thank you. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org

Re: inherit references features for antunit?

cuss antunit development. > > It is. > > > I was recently using antunit to test some ivy-based build scripts. > > This was complicated by the fact that I could not get the AntUnit > > scripts to inherit references from the parent project. Since you can > > inherit p

Re: inherit references features for antunit?

On 2010-04-05, Jason Trump wrote: > Not sure if this is the right forum to discuss antunit development. It is. > I was recently using antunit to test some ivy-based build scripts. > This was complicated by the fact that I could not get the AntUnit > scripts to inherit referen

inherit references features for antunit?

Hello, Not sure if this is the right forum to discuss antunit development. I was recently using antunit to test some ivy-based build scripts. This was complicated by the fact that I could not get the AntUnit scripts to inherit references from the parent project. Since you can inherit

AW: task that allows augmentation of previously declared references

> append/prepend isn't as far a departure from the current > model as would be > allowing complex expressions or arbitrary transformations. I havent followed the discussion, but read the "append to path" and this is possible. You can not append directly to a path, but because paths are - in contr

Re: task that allows augmentation of previously declared references

ss of the augment feature. > > > > > > On 25/03/2010 9:23 AM, Stefan Bodewig wrote: > > > >> On 2010-03-23, Antoine Levy Lambert wrote: > >> > >> > >> > >>> I prefer not to place any restriction on the

Re: task that allows augmentation of previously declared references

Point taken. But that sounds like an argument against the augment feature itself. If you are going to make exceptions, then things aren't really immutable at all. When properties were made immutable there had to be ugly little hacks like the prefix on tstamp to get around the fact there were ti

Re: task that allows augmentation of previously declared references

gment feature. > > > On 25/03/2010 9:23 AM, Stefan Bodewig wrote: > >> On 2010-03-23, Antoine Levy Lambert wrote: >> >> >> >>> I prefer not to place any restriction on the feature . >>> In fact references currently can be modified by user de

Re: task that allows augmentation of previously declared references

2010 9:23 AM, Stefan Bodewig wrote: On 2010-03-23, Antoine Levy Lambert wrote: I prefer not to place any restriction on the feature . In fact references currently can be modified by user developed ant tasks or script fragments. So you say since references can be overridden without aug

Re: task that allows augmentation of previously declared references

So you say since references can be overridden without augment it doesn't make any sense to restrict augment? Sounds reasonable. Yes. An attribute "final" on datatypes would make sense, if datatypes were internally changed, so that any calls to setters, add methods, ..

Re: task that allows augmentation of previously declared references

On 2010-03-23, Antoine Levy Lambert wrote: > I prefer not to place any restriction on the feature . > In fact references currently can be modified by user developed ant > tasks or script fragments. So you say since references can be overridden without augment it doesn't mak

Re: task that allows augmentation of previously declared references

Hi, I prefer not to place any restriction on the feature . In fact references currently can be modified by user developed ant tasks or script fragments. Regards, Antoine Stefan Bodewig wrote: On 2010-03-22, Matt Benson wrote: On Mar 22, 2010, at 5:42 AM, Jean-Louis Boudart wrote

Re: task that allows augmentation of previously declared references

I haven't been able to clearly > gauge the general direction of majority opinion on the "final" issue. I may be unable to gauge my own opinion on the "final" issue 8-) AFAIR I initially supported making references explicitly opt-in and can't remember the cons at all (

Re: task that allows augmentation of previously declared references

On Mar 22, 2010, at 5:42 AM, Jean-Louis Boudart wrote: Sorry for the delay. I really like the idea of being able to "augment" previously declared reference. There is many uses cases where it can be useful. For example, if ant can provides such feature it would simplify a lot the job in easy

Re: task that allows augmentation of previously declared references

Sorry for the delay. I really like the idea of being able to "augment" previously declared reference. There is many uses cases where it can be useful. For example, if ant can provides such feature it would simplify a lot the job in easyant for projects using many directories as source folder. They

Re: task that allows augmentation of previously declared references

n "attribute"? >>>> >>> >>> Agreed.  An alternative could be anything that contains a dash or any >>> other character that would be illegal in a Java method name (so you >>> can't have a set-method for it). >>> >>> &g

Re: task that allows augmentation of previously declared references

for it). Now, any id'd item would declare final=false if it wanted to be augmentable. This would require changes in the way we handle references, but would seem doable. +1 Stefan - To unsubscrib

Re: task that allows augmentation of previously declared references

r it). > > > Now, any id'd item would declare final=false if it wanted to be > > augmentable. This would require changes in the way we handle > > references, but would seem doable. > > +1 > > Stefan > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >

Re: task that allows augmentation of previously declared references

could be anything that contains a dash or any other character that would be illegal in a Java method name (so you can't have a set-method for it). > Now, any id'd item would declare final=false if it wanted to be > augmentable. This would require changes in the way we handl

Re: task that allows augmentation of previously declared references

be augmentable. This would require changes in the way we handle references, but would seem doable. On Mar 1, 2010, at 11:22 PM, Stefan Bodewig wrote: On 2010-02-25, Matt Benson wrote: I'd like to direct the Ant developers' attention to https:// issues.apache.org/bugzilla/show_bug

Re: task that allows augmentation of previously declared references

opt-in to so that not all references can be augmented. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org

Re: task that allows augmentation of previously declared references

On Feb 25, 2010, at 1:55 PM, Antoine Levy Lambert wrote: Matt Benson wrote: On Feb 25, 2010, at 10:53 AM, Dominique Devienne wrote: On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart wrote: Did you have any example to demonstrates the benefits of such task ? The benefits with conjunctio

Re: task that allows augmentation of previously declared references

Matt Benson wrote: On Feb 25, 2010, at 10:53 AM, Dominique Devienne wrote: On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart wrote: Did you have any example to demonstrates the benefits of such task ? The benefits with conjunction with could be important, in that you can "mix-in" specializ

Re: task that allows augmentation of previously declared references

On Feb 25, 2010, at 1:12 PM, Gilles Scokart wrote: On 25 February 2010 17:53, Dominique Devienne wrote: On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart wrote: Did you have any example to demonstrates the benefits of such task ? The benefits with conjunction with could be important, i

Re: task that allows augmentation of previously declared references

On 25 February 2010 17:53, Dominique Devienne wrote: > On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart > wrote: > > Did you have any example to demonstrates the benefits of such task ? > > The benefits with conjunction with could be important, in > that you can "mix-in" specialized pre-defined

Re: task that allows augmentation of previously declared references

On Feb 25, 2010, at 10:53 AM, Dominique Devienne wrote: On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart wrote: Did you have any example to demonstrates the benefits of such task ? The benefits with conjunction with could be important, in that you can "mix-in" specialized pre-defined buil

Re: task that allows augmentation of previously declared references

On Feb 25, 2010, at 10:00 AM, Gilles Scokart wrote: That's indeed quiet controversial. It moves ant from a declarative style to a more algorithmique language. What I dislike is that a target can have some side effect on datatype. Because id's are global, that will means that when you are us

Re: task that allows augmentation of previously declared references

On Thu, Feb 25, 2010 at 10:00 AM, Gilles Scokart wrote: > Did you have any example to demonstrates the benefits of such task ? The benefits with conjunction with could be important, in that you can "mix-in" specialized pre-defined builds dealing with specific concerns (like JAXB pre-compilation

Re: task that allows augmentation of previously declared references

That's indeed quiet controversial. It moves ant from a declarative style to a more algorithmique language. What I dislike is that a target can have some side effect on datatype. Because id's are global, that will means that when you are using an id into a task, you have to look at its definition

Re: task that allows augmentation of previously declared references

On Feb 25, 2010, at 8:56 AM, Dominique Devienne wrote: On Wed, Feb 24, 2010 at 10:39 PM, Matt Benson wrote: I'd like to direct the Ant developers' attention to https://issues.apache.org/bugzilla/show_bug.cgi?id=48798 for discussion. I'm hesitant to commit this outright because I anticipa

Re: task that allows augmentation of previously declared references

On Thu, Feb 25, 2010 at 8:56 AM, Dominique Devienne wrote: > On Wed, Feb 24, 2010 at 10:39 PM, Matt Benson wrote: >> I'd like to direct the Ant developers' attention to >> https://issues.apache.org/bugzilla/show_bug.cgi?id=48798 for discussion. BTW, I think the list is a better place for the dis

Re: task that allows augmentation of previously declared references

On Wed, Feb 24, 2010 at 10:39 PM, Matt Benson wrote: > I'd like to direct the Ant developers' attention to > https://issues.apache.org/bugzilla/show_bug.cgi?id=48798 for discussion. >  I'm hesitant to commit this outright because I anticipate this being > somewhat controversial.  If noone responds

task that allows augmentation of previously declared references

I'd like to direct the Ant developers' attention to https:// issues.apache.org/bugzilla/show_bug.cgi?id=48798 for discussion. I'm hesitant to commit this outright because I anticipate this being somewhat controversial. If noone responds I'll just assume it's not controversial and act accor

DO NOT REPLY [Bug 43716] - position of import task cannot be after their references

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 43716] - position of import task cannot be after their references

gzilla/show_bug.cgi?id=43716 --- Additional Comments From [EMAIL PROTECTED] 2007-10-29 03:55 --- I think we will probably mark as a WONTFIX; changes to reference resolution and/or import are the root cause. the key thing is that you shouldnt have any forward references in a build file at al

DO NOT REPLY [Bug 43716] New: - position of import task cannot be after their references

gzilla/show_bug.cgi?id=43716 Summary: position of import task cannot be after their references Product: Ant Version: 1.7.0 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component

DO NOT REPLY [Bug 42482] - ant and subant improperly passes references to macrodefs and scriptdefs to the child script

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 42483] New: - subant incorrectly complaining about circular references

gzilla/show_bug.cgi?id=42483 Summary: subant incorrectly complaining about circular references Product: Ant Version: 1.7.0 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Core

DO NOT REPLY [Bug 42482] New: - ant and subant improperly passes references to macrodefs and scriptdefs to the child script

gzilla/show_bug.cgi?id=42482 Summary: ant and subant improperly passes references to macrodefs and scriptdefs to the child script Product: Ant Version: 1.7.0 Platform: Other OS/Version: other Status: NEW Se

Re: references: backwards compatibility

Dominique Devienne wrote: Ok, I will get my id reference stuff ready. I do not think that we need a commandline arg or a property, the only thing that is needed is a warning like DD's Warning: Reference y has not been set at runtime, but was found during build file parsing, attempting to resolve

Re: references: backwards compatibility

is bad. That's why Ant is difficult to use for large builds, > because the build becomes exponentially difficult to troubleshoot > when something goes wrong. > > I think we need to move toward a policy system where Ant's behavior > can be made safer and more deterministic

Re: references: backwards compatibility

am afraid that ant has a lot of surprises! And this is bad. That's why Ant is difficult to use for large builds, because the build becomes exponentially difficult to troubleshoot when something goes wrong. I think we need to move toward a policy system where Ant's behavior can be made s

Re: references: backwards compatibility

ng specified out the build, use a CLI switch or the setting of a user property as proposed by Stefan. I am proposing not complete BC, it is more a fall-back behaviour, if a reference is requested *and* not found, then the id references are checked and if found there, a copy of the UE will be exec

Re: references: backwards compatibility

Ok, I will get my id reference stuff ready. I do not think that we need a commandline arg or a property, the only thing that is needed is a warning like DD's Warning: Reference y has not been set at runtime, but was found during build file parsing, attempting to resolve. Future versions of Ant ma

Re: references: backwards compatibility

Peter Reilly wrote: On 10/17/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote: On Mon, 16 Oct 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > what do other people think? I'm with Steve here. We need a way to get around broken build files of projects you want to build but don't own. I don't care

Re: references: backwards compatibility

On 10/17/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote: On Mon, 16 Oct 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > what do other people think? I'm with Steve here. We need a way to get around broken build files of projects you want to build but don't own. I don't care much whether it is a

Re: references: backwards compatibility

On Mon, 16 Oct 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > what do other people think? I'm with Steve here. We need a way to get around broken build files of projects you want to build but don't own. I don't care much whether it is a property (would be in line with other things we've introd

Re: references: backwards compatibility

I would make it a non-failing warning for ant1.7, maybe an error in 1.8. I can see where you are coming from, but I disagree on accepting the old build files, or at least not without a --keep-old-broken-behavior switch on the command line, instead of yet another magic property. --DD --

Re: references: backwards compatibility

reated by third party projects I download and build, just because they (like me) got lazy. The fact that Ant has had a bad but stable way of declaring references mean that we need to think of how best to move people of it. I would make it a non-failing warning for ant1.7, maybe

Re: references: backwards compatibility

Hi Dominique, this sounds like a good idea. Regards, Antoine Original-Nachricht Datum: Mon, 16 Oct 2006 09:58:58 -0500 Von: "Dominique Devienne" <[EMAIL PROTECTED]> An: "Ant Developers List" Betreff: Re: references: backwards compatibility > &

Re: references: backwards compatibility

On 10/16/06, Dominique Devienne <[EMAIL PROTECTED]> wrote: > WARNING: reference y has not been set, attempting to resolve > > [echo] y is C:\Documents and Settings\reilly\learning\a\refs\build.xml I really think we should break BC here, with a good error message. Keeping the old behavior wou

Re: references: backwards compatibility

WARNING: reference y has not been set, attempting to resolve [echo] y is C:\Documents and Settings\reilly\learning\a\refs\build.xml I really think we should break BC here, with a good error message. Keeping the old behavior would re-open the bug about the not-defined-at-runtime ref being us

Re: references: backwards compatibility

the moment working on a solution along this lines: have an IdReferences that keeps track of the ids. if an id cannot be resolved when using project.getReference(id), check the id references and resolve it the old - fashioned way with a warning: y is ${myPath} x: WARNI

Re: references: backwards compatibility

I think some kind of property ant.policy.references.inline or something could be set to turn on old behaviour We've somehow never done it, but maybe we should have a version attribute on , and increment it whenever we introduce a BC breaking change? I'm not sure it's practical to provide both t

references: backwards compatibility

My test code broke this am, since the update. The cause? I was not explicitly depending on something that had needed run.classpath defined, but the automatic-reference definition stuff had been letting me get away with a (defective) build file. I did fix it, but wasted some time before decid

DO NOT REPLY [Bug 37688] - script task confuses Ant references

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: VOTE: deferring resolving of references

It has been a week since the vote started, there are 6 +1s, 0 0s and 0 -1s, Unless there is a -1, I will commit the change later today. Peter On 9/29/06, Dominique Devienne <[EMAIL PROTECTED]> wrote: On 9/29/06, Martijn Kruithof <[EMAIL PROTECTED]> wrote: > Peter Reilly wrote: > > Impact: It i

Re: VOTE: deferring resolving of references

On 9/29/06, Martijn Kruithof <[EMAIL PROTECTED]> wrote: Peter Reilly wrote: > Impact: It is a one-line change. > Influence release of 1.7: I do not think so. In that case +1 +1. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED]

Re: deferring resolving of references

Hi, +1 from me Antoine - Original Message - From: "Peter Reilly" <[EMAIL PROTECTED]> To: "Ant Developers List" Sent: Friday, September 29, 2006 5:23 PM Subject: VOTE: deferring resolving of references > Hi, I started a thead last week that did not end

Re: VOTE: deferring resolving of references

Peter Reilly wrote: Impact: It is a one-line change. Influence release of 1.7: I do not think so. (I think that we need to release an ant 1.7beta3 soon, freeze commits after that (or branch) and try to get as many users to try it out.) There are BC issues: some scripts may depend on references

Re: VOTE: deferring resolving of references

Impact: It is a one-line change. Influence release of 1.7: I do not think so. (I think that we need to release an ant 1.7beta3 soon, freeze commits after that (or branch) and try to get as many users to try it out.) There are BC issues: some scripts may depend on references defined in tasks that

Re: VOTE: deferring resolving of references

+1 -Matt - Original Message From: Peter Reilly <[EMAIL PROTECTED]> To: Ant Developers List Sent: Friday, September 29, 2006 10:23:22 AM Subject: VOTE: deferring resolving of references Hi, I started a thead last week that did not end in a conclusion. should we defer res

Re: VOTE: deferring resolving of references

Peter Reilly wrote: Hi, I started a thead last week that did not end in a conclusion. should we defer resolving references until runtime: original message " Currently in ant, there is two steps in processing a project build file, a parsing step and an execution step. In the parsing step

Re: VOTE: deferring resolving of references

+1. This is one of illogical places left in ANT. - Alexey. On 9/29/06, Peter Reilly <[EMAIL PROTECTED]> wrote: Hi, I started a thead last week that did not end in a conclusion. should we defer resolving references until runtime: original message " Currently in ant, there is t

VOTE: deferring resolving of references

Hi, I started a thead last week that did not end in a conclusion. should we defer resolving references until runtime: original message " Currently in ant, there is two steps in processing a project build file, a parsing step and an execution step. In the parsing step a DOM like structu

Re: Deferring references

On 9/25/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote: On Mon, 25 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > On 9/25/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote: >> >> On Fri, 22 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> >> wrote: >> >> > I propose that we defer handing id's until the

Re: Deferring references

On Mon, 25 Sep 2006, Dominique Devienne <[EMAIL PROTECTED]> wrote: > >> I feel uncomfortable about changing this, even though you are >> probably right that it it should better be changed. > > Is this the -0 I feel I read, or a stronger -1 Stefan? a -0, I'm more vocal with a -1 ;-) Stefan

Re: Deferring references

I feel uncomfortable about changing this, even though you are probably right that it it should better be changed. Is this the -0 I feel I read, or a stronger -1 Stefan? --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

Re: Deferring references

On Mon, 25 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > On 9/25/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote: >> >> On Fri, 22 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> >> wrote: >> >> > I propose that we defer handing id's until the processing >> > stage. >> >> Will probably break somethi

Re: Deferring references

I really cannot see the use-case described by the example. I would not think that there are any examples in the "wild". Oh, I'm sure there are! Yet I support your proposed change Peter. I also consider this usage of id an anti-pattern, and I'm fine to breaking BC in this case to fix once and for

Re: Deferring references

On 9/25/06, Stefan Bodewig <[EMAIL PROTECTED]> wrote: On Fri, 22 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > I propose that we defer handing id's until the processing > stage. Will probably break something like

Re: Deferring references

On Fri, 22 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > I propose that we defer handing id's until the processing > stage. Will probably break something like

Re: Deferring references

+1 for this change, Antoine - Original Message - From: "Peter Reilly" <[EMAIL PROTECTED]> To: "Ant Developers List" Sent: Friday, September 22, 2006 4:00 PM Subject: Deferring references > Currently in ant, there is two steps in processing > a project b

Re: Deferring references

--- Peter Reilly <[EMAIL PROTECTED]> wrote: > On 9/22/06, Matt Benson <[EMAIL PROTECTED]> > wrote: > > > > --- Peter Reilly <[EMAIL PROTECTED]> > wrote: > > [SNIP] > > > I propose that we defer handing id's until the > > > processing > > > stage. > > > > > > The change to do this is very small. >

Re: Deferring references

On 9/22/06, Matt Benson <[EMAIL PROTECTED]> wrote: --- Peter Reilly <[EMAIL PROTECTED]> wrote: [SNIP] > I propose that we defer handing id's until the > processing > stage. > > The change to do this is very small. > [SNIP] > I have have played a little with this and everthing > seems > to work f

Re: Deferring references

--- Peter Reilly <[EMAIL PROTECTED]> wrote: [SNIP] > I propose that we defer handing id's until the > processing > stage. > > The change to do this is very small. > [SNIP] > I have have played a little with this and everthing > seems > to work fine. > I would imagine we couldn't call this change

Deferring references

Currently in ant, there is two steps in processing a project build file, a parsing step and an execution step. In the parsing step a DOM like structure of Targets and UnknownElements are build up. These targets and unknown elements are then processed in the execution step. This model works quite o

DO NOT REPLY [Bug 37688] - script task confuses Ant references

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: copying references

ne else) have an opinion on DD's assertion that the concrete use-case (modifying imported references) could be better solved by scoping imported references as targets? [1] -Matt [1] http://marc.theaimsgroup.com/?l=ant-dev&m=115703947632596&w=2 > > Stefan > >

Re: copying references

On Thu, 31 Aug 2006, Matt Benson <[EMAIL PROTECTED]> wrote: > All: shouldn't Ant have an e.g. task? We probably never felt the need for it, but why not. I'm not sure about the name since copy implies cloning to me. Something with "alias" in its name? Stefan --

Re: copying references

red result either: > > > > > > > > > > > > > > > > Why doesn't this work? It should, no? > Sure, having the use a new id is not great, but... > > > > > > You should still get a circular reference because >

Re: copying references

is doesn't yield the desired result either: Why doesn't this work? It should, no? Sure, having the use a new id is not great, but... You should still get a circular reference because of the way references are resolved. Yep, circular it is. The only way is:

Re: copying references

--- Dominique Devienne <[EMAIL PROTECTED]> wrote: > On 8/31/06, Matt Benson <[EMAIL PROTECTED]> > wrote: > > DD, what was that task you had for doing something > > with references at a different time than Ant > normally > > would? Seems like it is attached

Re: copying references

On 8/31/06, Matt Benson <[EMAIL PROTECTED]> wrote: DD, what was that task you had for doing something with references at a different time than Ant normally would? Seems like it is attached to a BZ issue someplace... Do you know what I'm talking about? Yes, it's called

copying references

DD, what was that task you had for doing something with references at a different time than Ant normally would? Seems like it is attached to a BZ issue someplace... Do you know what I'm talking about? All: shouldn't Ant have an e.g. task? Example, given the custom foo type:

Re: Re: Is there a way I can edit out-of-date external references myself?

Thanks Martijn, Antoine Original-Nachricht Datum: Mon, 19 Jun 2006 19:56:41 +0200 Von: Martijn Kruithof <[EMAIL PROTECTED]> An: Ant Developers List Betreff: Re: Is there a way I can edit out-of-date external references myself? > done > > Antoine Levy-

Re: Is there a way I can edit out-of-date external references myself?

AIL PROTECTED]> An: dev@ant.apache.org Betreff: Is there a way I can edit out-of-date external references myself? Is there a way I can do this myself? Thanks, The Wabbit --- [ SNIP ] --- Hi all, The AntXtras project has moved to SF.net. The current website is now available a

Re: Is there a way I can edit out-of-date external references myself?

etreff: Is there a way I can edit out-of-date external references myself? > Is there a way I can do this myself? > > Thanks, > The Wabbit > > --- [ SNIP ] --- > > Hi all, > > The AntXtras project has moved to SF.net. The current website is > now available

Is there a way I can edit out-of-date external references myself?

Is there a way I can do this myself? Thanks, The Wabbit --- [ SNIP ] --- Hi all, The AntXtras project has moved to SF.net. The current website is now available at http://antxtras.sourceforge.net. Can someone please replace the "JWare/AntXtras Foundation" External Tools subsection with the foll

DO NOT REPLY [Bug 37688] - script task confuses Ant references

nfuses Ant |confuses Ant references |references --- Additional Comments From [EMAIL PROTECTED] 2005-12-02 10:50 --- Just changing the name of bug as it is a general script/reference problem. It is most likely related to the way references are processed - they are

DO NOT REPLY [Bug 37744] - xslt task doesn't report invalid entity references

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37744] New: - xslt task doesn't report invalid entity references

gzilla/show_bug.cgi?id=37744 Summary: xslt task doesn't report invalid entity references Product: Ant Version: 1.6.5 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component:

DO NOT REPLY [Bug 37688] - script task with beanshell confuses Ant references

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37688] New: - script task with beanshell confuses Ant references

gzilla/show_bug.cgi?id=37688 Summary: script task with beanshell confuses Ant references Product: Ant Version: 1.6.5 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Core

DO NOT REPLY [Bug 32631] - allow includes / excludes for fileset references

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: References

--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Mon, 11 Apr 2005, Matt Benson > <[EMAIL PROTECTED]> wrote: > > > Ever noticed that every Ant type that supports the > > id/refid pattern must include a load of custom > code? > > Why? Wouldn't it be possible in UE to check all > > DataType subcl

Re: References

On Mon, 11 Apr 2005, Dominique Devienne <[EMAIL PROTECTED]> wrote: > So on second thought, it sounds doable. The only possible break of > BC I can foresee ATM would be for custom types, outside of Ant, > which broke the unwritten rule that no attributes/elements are > allowed once one uses refdid=

Re: References

On Mon, 11 Apr 2005, Matt Benson <[EMAIL PROTECTED]> wrote: > Ever noticed that every Ant type that supports the > id/refid pattern must include a load of custom code? > Why? Wouldn't it be possible in UE to check all > DataType subclass elements for refid, validate no > other attributes/element

  1   2   >