Parsing multiple ivy.xml file
Hi, I am Kathirvelu working at July Systems as an engineer. I am going to use Ivy for my new project. The requirement is once we run ant command it will download some zip from our remote repository. Each zip contains a Ivy.xml, need to parse all Ivy.xml to find the dependencies. Presently I don’t know whether the Ivy has support for this. How can I implemented this. Waiting for your reply. Thanks *Kathirvelu U* ENGINEER – PRODUCT ENGINEERING [image: July_systems_mail_4] * * *julysystems.com* http://www.julysystems.com* |* *M*: +91 9244689777 | *T*: +91 80 41105859 | kat...@julysystems.com * * *Los Angeles*: 1530 7th Street, Suite 100 Santa Monica, CA 90401 USA *New York*: 1140 Avenue of the Americas, 10th Floor, New York, NY 10036 USA *Bangalore*: Maruthi Chambers, No 17/4C, 4th Floor, Roopena Agrahara, Hosur Road, Bangalore 560 068 INDIA This email message is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original document.
Re: svn commit: r1151473 - in /ant/core/trunk: WHATSNEW src/main/org/apache/tools/ant/taskdefs/AugmentReference.java
Removing my figurative hat! The bit of time I had spent looking at
this didn't bear fruit; can't believe it was this simple. Thanks
Stefan!
Matt
On Wed, Jul 27, 2011 at 9:08 AM, bode...@apache.org wrote:
Author: bodewig
Date: Wed Jul 27 14:08:00 2011
New Revision: 1151473
URL: http://svn.apache.org/viewvc?rev=1151473view=rev
Log:
restore RCW id once augment has performed its job so it can be reused by
other targets. PR 50894
Modified:
ant/core/trunk/WHATSNEW
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/AugmentReference.java
Modified: ant/core/trunk/WHATSNEW
URL:
http://svn.apache.org/viewvc/ant/core/trunk/WHATSNEW?rev=1151473r1=1151472r2=1151473view=diff
==
--- ant/core/trunk/WHATSNEW (original)
+++ ant/core/trunk/WHATSNEW Wed Jul 27 14:08:00 2011
@@ -73,6 +73,10 @@ Fixed bugs:
* sync didn't work properly when working on resource collections.
Bugzilla Report 51462.
+ * augment cause a NullPointerException if it was used in a target
+ that was invoked by multiple targets from the command line.
+ Bugzilla Report 50894.
+
Other changes:
--
Modified:
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/AugmentReference.java
URL:
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/AugmentReference.java?rev=1151473r1=1151472r2=1151473view=diff
==
---
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/AugmentReference.java
(original)
+++
ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/AugmentReference.java
Wed Jul 27 14:08:00 2011
@@ -70,4 +70,26 @@ public class AugmentReference extends Ta
wrapper.setElementTag(augmented reference \ + id + \);
}
}
+
+ /**
+ * Overridden to restore the wrapper once it is no longer needed.
+ * @since Ant 1.8.3
+ */
+ public void execute() {
+ restoreWrapperId();
+ }
+
+ /**
+ * Needed if two different targets reuse the same instance.
+ * @see https://issues.apache.org/bugzilla/show_bug.cgi?id=50894
+ */
+ private synchronized void restoreWrapperId() {
+ if (id != null) {
+ log(restoring augment wrapper + id, Project.MSG_DEBUG);
+ RuntimeConfigurable wrapper = getWrapper();
+ wrapper.setAttribute(id, id);
+ wrapper.setElementTag(getTaskName());
+ }
+ }
+
}
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Limit PropertyHelper delegates to a certain scope?
I have a situation where I'm retrofitting some old code to use the PropertyHelper delegates that where added in Ant 1.8; in particular I need to limit that scope to which a certain delegate is active. I know how to add a delegate but there doesn't seem to be any way of removing a delegate once it's no longer needed: they seem to persist forever. As a stop-gap I've added a way to deactivate my delegate such that it will always return the proper values so that the next delegate will be invoked, but that seems like a poor work around. Is there a better way to do this? Jeffrey E. (Jeff) Care ca...@us.ibm.com IBM WebSphere Application Server WAS Release Engineering
Re: Limit PropertyHelper delegates to a certain scope?
Hi, Jeff! Seems like it's been awhile. :) Off the top of my head the only thing that occurs to me are ant/antcall/subant: the tasks that create a new project. :/ Matt On Wed, Jul 27, 2011 at 1:39 PM, Jeffrey E Care ca...@us.ibm.com wrote: I have a situation where I'm retrofitting some old code to use the PropertyHelper delegates that where added in Ant 1.8; in particular I need to limit that scope to which a certain delegate is active. I know how to add a delegate but there doesn't seem to be any way of removing a delegate once it's no longer needed: they seem to persist forever. As a stop-gap I've added a way to deactivate my delegate such that it will always return the proper values so that the next delegate will be invoked, but that seems like a poor work around. Is there a better way to do this? Jeffrey E. (Jeff) Care *ca...@us.ibm.com* ca...@us.ibm.com IBM WebSphere Application Server WAS Release Engineering [image: WebSphere Mosiac] [image: WebSphere Brandmark]
Re: Limit PropertyHelper delegates to a certain scope?
Yeah, I've been working on other projects for quite a while but recently I got thrown back into low-level build stuff. I'm still trying to push some Ant patches through IBM's legal approval process so if/when that ever happens you're likely to see some more of me. Anyway, I figured that there was no way to remove delegates, so my hacky work around will have to do for now I guess. I'm curious to get the community's thoughts on this: would delegate removal be a valuable thing to have? If there's a consensus that delegate removal is a good thing then I'm willing to work on it and submit it with the other patches that I have in the pipe. Jeffrey E. (Jeff) Care ca...@us.ibm.com IBM WebSphere Application Server WAS Release Engineering From: Matt Benson gudnabr...@gmail.com To: Ant Developers List dev@ant.apache.org Date: 07/27/2011 02:48 PM Subject:Re: Limit PropertyHelper delegates to a certain scope? Hi, Jeff! Seems like it's been awhile. :) Off the top of my head the only thing that occurs to me are ant/antcall/subant: the tasks that create a new project. :/ Matt On Wed, Jul 27, 2011 at 1:39 PM, Jeffrey E Care ca...@us.ibm.com wrote: I have a situation where I'm retrofitting some old code to use the PropertyHelper delegates that where added in Ant 1.8; in particular I need to limit that scope to which a certain delegate is active. I know how to add a delegate but there doesn't seem to be any way of removing a delegate once it's no longer needed: they seem to persist forever. As a stop-gap I've added a way to deactivate my delegate such that it will always return the proper values so that the next delegate will be invoked, but that seems like a poor work around. Is there a better way to do this? Jeffrey E. (Jeff) Care *ca...@us.ibm.com* ca...@us.ibm.com IBM WebSphere Application Server WAS Release Engineering [image: WebSphere Mosiac] [image: WebSphere Brandmark]
Re: Limit PropertyHelper delegates to a certain scope?
Seems like scoped delegates would be handy, perhaps more so than straight-up delegate removal. It might be possible to use the existing notion of property scopes to support this. Matt On Wed, Jul 27, 2011 at 2:25 PM, Jeffrey E Care ca...@us.ibm.com wrote: Yeah, I've been working on other projects for quite a while but recently I got thrown back into low-level build stuff. I'm still trying to push some Ant patches through IBM's legal approval process so if/when that ever happens you're likely to see some more of me. Anyway, I figured that there was no way to remove delegates, so my hacky work around will have to do for now I guess. I'm curious to get the community's thoughts on this: would delegate removal be a valuable thing to have? If there's a consensus that delegate removal is a good thing then I'm willing to work on it and submit it with the other patches that I have in the pipe. Jeffrey E. (Jeff) Care *ca...@us.ibm.com* ca...@us.ibm.com IBM WebSphere Application Server WAS Release Engineering [image: WebSphere Mosiac] [image: WebSphere Brandmark] From:Matt Benson gudnabr...@gmail.com To:Ant Developers List dev@ant.apache.org Date:07/27/2011 02:48 PM Subject:Re: Limit PropertyHelper delegates to a certain scope? -- Hi, Jeff! Seems like it's been awhile. :) Off the top of my head the only thing that occurs to me are ant/antcall/subant: the tasks that create a new project. :/ Matt On Wed, Jul 27, 2011 at 1:39 PM, Jeffrey E Care ca...@us.ibm.com wrote: I have a situation where I'm retrofitting some old code to use the PropertyHelper delegates that where added in Ant 1.8; in particular I need to limit that scope to which a certain delegate is active. I know how to add a delegate but there doesn't seem to be any way of removing a delegate once it's no longer needed: they seem to persist forever. As a stop-gap I've added a way to deactivate my delegate such that it will always return the proper values so that the next delegate will be invoked, but that seems like a poor work around. Is there a better way to do this? Jeffrey E. (Jeff) Care *ca...@us.ibm.com* ca...@us.ibm.com IBM WebSphere Application Server WAS Release Engineering [image: WebSphere Mosiac] [image: WebSphere Brandmark]
Re: svn commit: r1151473 - in /ant/core/trunk: WHATSNEW src/main/org/apache/tools/ant/taskdefs/AugmentReference.java
On 2011-07-27, Matt Benson wrote: The bit of time I had spent looking at this didn't bear fruit; can't believe it was this simple. It took quite a few System.err.printlns to get there 8-) Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Limit PropertyHelper delegates to a certain scope?
On 2011-07-27, Matt Benson wrote: Seems like scoped delegates would be handy, perhaps more so than straight-up delegate removal. +1 Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
