This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Pipeline as Code and have Mohamed Labouardy on-line!
See this thread for details.
Win a copy of Pipeline as Code this week in the Cloud/Virtualization forum!

Jacob Schuetze

Greenhorn
+ Follow
since Jun 27, 2001
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jacob Schuetze

Originally posted by Chris Reeves:
Your other option here is to just fail the build if the property hasn't been set. Then you develpers will be forced to go in and set the property. It's not a great solution if you really want to change that parameter on the fly, but it would work.
I'm not sure what this parameter will be used for, so I don't know what other solutions to offer.


The original goal was to be able to have a build.xml file that would do a checkout from VisualSourceSafe (new optional tags in 1.5) and then build the code. The idea was that a developer needing to work on a certain tag branch would maybe want to set a property. If, for example, a developer is setting up a new environment just from the build.xml, they would want to enter a specific tag once via <input .../> (or just get latest, which I handle separately. At any rate, I continued along the line of my last post with the depends and multiple matching targets with if= and unless=, and it now works. I have also created a custom input using Swing so that the input tag works in my IDE also (eclipse). Now if the property is set in the build.xml, I run the checkout target and it gets what I specified. If it's NOT set, I run the checkout target and I get a Swing prompt for a label to get, and it properly sets the target property and checks out the labeled code. Pretty cool, now that it works
18 years ago
Thank you for looking into it. From what I've found on the web about similar problems, there's some speculation that it may be tied to version of Xerces in the classpath.
I was seeing this problem primarily on eclipse, but then also on my development workstation at work. I tried similar code here at home wit Ant 1.5 and then in eclipse and had success, but only when I do the input in the depends. The scope of the property seems to only be the target. If I set the property via antcall, as in my example above, it doesn't get set. If I set it in a depends target, it gets included in the calling target. Here's a thought I haven't tried yet...

even if this works, it feels hacky because our "switch" is a property set elsewhere, then we try to run all targets (which would do the same thing, ultimately) and rely on the 'if' and 'unless' in the targets to ensure only one runs.
18 years ago
I'm using Ant 1.5 and using the input task. I'm having some problems getting a property set. Here're the relevant snippets:

I have vssCheckLabel, because I want to allow developers to hard code a label in their own build.xml. At the same time, I want to prompt for it if it doesn't exist. The problem I'm having is that if it's not set, then checkout.has.vss.proj.label stays unset as expected and promptForVssLabel properly runs. After entering the input, the echo with message of "Label2:${checkout.vss.proj.label}" displays, with my new input in checkout.vss.proj.label, but when control returns to vssGetLabel, ${checkout.vss.proj.label} is now unset and the echo with "Label2:${checkout.vss.proj.label}" prints out literally "Label2:${checkout.vss.proj.label}", without property value replacement.
Any ideas?
Thanks,
Jacob
[ July 16, 2002: Message edited by: Jacob Schuetze ]
18 years ago

By the way, my comments here are my own initiative and were not requested by Jacob.


Not requested, but both unexpected and very much appreciated! Thanks!

[This message has been edited by Jacob Schuetze (edited June 28, 2001).]
19 years ago
I am a senior Java developer with extensive experience in various Java related technologies. I also have extensive contracting experience. I am, however, searching for an FTE position, but would consider a contract position as well. I live in north Denver, Colorado and am not interested in relocating at this time, but willing to consider positions that require a fair amount of domestic and/or international travel.
My resume can be viewed online here
Thanks for your serious consideration.
------------------
Quid quid Latine dictum sit, altum viditur
Whatever is said in Latin sounds important.

[This message has been edited by Jacob Schuetze (edited June 27, 2001).]
[This message has been edited by Jacob Schuetze (edited June 27, 2001).]
19 years ago