Re: New conditional attributes on use of macrodef?

; On Dec 14, 2013, at 5:39 PM, Antoine Levy Lambert wrote: > > > Hello Richard, > > > > this is a bug. I have entered it in bugzilla id 55885. > > > > Regards, > > > > Antoine > > On Dec 9, 2013, at 9:22 AM, Steele, Richard wrote: > &g

New conditional attributes on use of macrodef?

I can't seem to get the new if: and unless: attributes working on uses of macrodef. For example: hi If I do "ant hi" from the command line the script runs to completion, and as expected, there's no output: C:\conditional-tests>ant

Re: Unexpected behavior

Confirmed: a target "ab" that antcalls a and b individually doesn't exhibit the same problem. On Mon, Dec 2, 2013 at 12:12 AM, Stefan Bodewig wrote: > On 2013-12-01, Steele, Richard wrote: > > > Thanks for the confirmation, I created bug #55831. > > Thanks. >

Re: Unexpected behavior

Thanks for the confirmation, I created bug #55831. I'm assuming this problem will also rear up with our (legacy build's mis)use of , so this is actually pretty critical for us. Is there any hope of a fix? On Sat, Nov 30, 2013 at 11:20 AM, Stefan Bodewig wrote: > On 2013-

Unexpected behavior

I've run into an odd behavior that I'm assuming is a defect but I'd like to confirm. With this build file: If I invoke target "b" I get a response I expect: C

Re: Feature request: if/unless on command line arguments

On Fri, Feb 17, 2012 at 8:30 AM, Dominique Devienne wrote: > >> From: "Steele, Richard" > >> I think it would be convenient to have command-line arguments take > optional > >> if/unless attributes that work much like those on targets. > > On F

Feature request: if/unless on command line arguments

I think it would be convenient to have command-line arguments take optional if/unless attributes that work much like those on targets. My use case is with the task where I want to conditionally pass in an -Xlint option: .

Re: ProjectHelper2 fails to close input source after parsing imported document?

On Tue, Oct 25, 2011 at 1:24 PM, Steele, Richard wrote: > On Tue, Oct 25, 2011 at 11:58 AM, Stefan Bodewig wrote: > > You could try using a different XML parser (Saxon's AElfred, maybe). >> > > I might do that just to prove my analysis, but I was hoping to avoid havin

Re: ProjectHelper2 fails to close input source after parsing imported document?

t; imported document? > > On 2011-10-25, Steele, Richard wrote: > > > I'm chasing a defect with one of my custom Ant tasks. To summarize, the > > task uses ImportTask under the hood to import build scripts. These > scripts > > can come from jar files downloaded

Re: ProjectHelper2 fails to close input source after parsing imported document?

On Tue, Oct 25, 2011 at 11:58 AM, Stefan Bodewig wrote: > On 2011-10-25, Steele, Richard wrote: > > > I'm chasing a defect with one of my custom Ant tasks. To summarize, the > > task uses ImportTask under the hood to import build scripts. These > scripts > > ca

ProjectHelper2 fails to close input source after parsing imported document?

I'm chasing a defect with one of my custom Ant tasks. To summarize, the task uses ImportTask under the hood to import build scripts. These scripts can come from jar files downloaded via Ivy. The problem I'm running into is that, at least on Windows, I'm unable to clean the project because Ant ha

Re: NPE thrown from ProjectHelper2.parse() when parsing from URL

On Wed, Sep 28, 2011 at 11:48 AM, Stefan Bodewig wrote: > I'm pretty sure I recall this being discussed on the dev list, so it is > something the dev community is aware of. ProjectHelper2 still mostly > deals with files only, URL support is largely there for antlibs and > import/include. > That

NPE thrown from ProjectHelper2.parse() when parsing from URL

Running Ant 1.8.2 on Windows XP, I'm writing a task that returns a string resource collection of target names in a project. Well, attempting to write one. I'm running into problems when the build file I'm parsing is from a URL instead of a File. The main method that I have looks like this:

Re: Bug 50894: Invoking multiple targets that share the same dependency to augment a path causes NullPointerException

Yikes, that was fast. Thanks! Rich On Wed, Jul 27, 2011 at 10:27 AM, Stefan Bodewig wrote: > On 2011-07-27, Stefan Bodewig wrote: > > > On 2011-07-27, Stefan Bodewig wrote: > > >> On 2011-07-27, Steele, Richard wrote: > > >>> I keep bumping into the issu

Bug 50894: Invoking multiple targets that share the same dependency to augment a path causes NullPointerException

I keep bumping into the issue I documented in bug 50894but there's no feedback about it. Here's the description: Using this build file:

Re: Finding an available port number

This doesn't directly answer your question, but Hudson/Jenkins does have the port allocator plugin which does much as you suggest, but of course only in the context of running a job. See https://wiki.jenkins-ci.org/display/JENKINS/Port+Allocator+Plugin. Rich On Mon, May 2, 2011 at 8:12 PM, Danie

Re: Loading resource or property files embedded in jar file that distributes shared build files?

Thanks, actually your suggestion led me to find that I can use a resource using a baseResource of ${ant.file.project-name} with a relative path of "/foo", and this works well. I too had to create a variation that could load the same resource using a resource, but it wasn't too hard. I'll proba

Loading resource or property files embedded in jar file that distributes shared build files?

I've created a reusable set of build files using the technique I outlined at http://stackoverflow.com/questions/5124726/what-are-some-good-ways-to-distribute-a-common-ant-file-to-be-included-in-builds/5168745#5168745. This technique relies heavily on Ant 1.8 importing files from the classpath rathe

Re: Using as a resource collection in

Hi Matt no need to apologize for the delay. I have mixed feelings about re-purposing the "id" attribute to use as the resource name. To me they're different things: I might want to use the id for internal use and therefore want to conform to some kind of naming convention, but I need a different

Re: Enhancement: allow a in an filter

I created 51044. Thanks, Rich On Tue, Apr 5, 2011 at 8:25 AM, Antoine Levy-Lambert wrote: > On 4/1/2011 7:51 AM, Steele, Richard wrote: > >> As implemented it looks like expands all properties. >> I'd >> really like if I could embed a in it to control whi

Enhancement: allow a in an filter

As implemented it looks like expands all properties. I'd really like if I could embed a in it to control which properties get expanded. Is there a technical reason this won't work? If not, I'll gladly file an enhancement request. By the way this is related to bug 9481 (Add a "prefix" attribut

Using as a resource collection in

I'm trying to use as a resource collection in a and found that it doesn't work so well. First, an example: This creates a zip file with multiple entries named "concat (C:", not a single entry containing the CHANGES.txt file. (The reason I'm playing with as a resource collect

Re: Wisdom of using ":" in property name

s a better choice? What do others do with very large, reusable build "suites" broken into multiple separate build files? (Beside switching tools, of course. :-) Sorry for griping. Ant 1.8 has been a revelation to me and I've been able to do so much more with so little I should

Re: Wisdom of using ":" in property name

Peter > > > > > > On Tue, Feb 1, 2011 at 2:37 PM, Vimil Saju wrote: > >> you're nuts, don't use : in property names! :P > >> > >> --- On Tue, 2/1/11, Steele, Richard wrote: > >> > >>> From: Steele, Richard > >

Wisdom of using ":" in property name

For better or for worse, I'm using ":" as a separator character in my property names as part of a set of reusable build files. The part before the ":" indicates which build file the property is defined in. I've come across at least one incompatibility doing this, however, and that is with the Bun

Re: Sharing Ivy settings file amongst developpers

Same here. We rejected putting in the SCM repo because we want our settings shared across all projects, and at this company each project is in its own repo. We also have a shared (common) set of configurations that projects can include, as well as the ivy.jar file on the same server. You should