Ant tip: verbose mode tells you all un-set properties

Just realized that running Ant in verbose mode will tell you all properties that are not properly set. Just search the output for "has not been set".

Because of it, I’m now fixing a lot of subtle bugs in my build scripts that have been lingering for many months.

All the lines in the XBN-Java, Template Feather, Codelet master build that I just ran, containing “has not been set”:

Property "pom_xml_dest" has not been set
Property "dir_classes_codelet" has not been set
Property "main_or_gitonly" has not been set
Property "dir_${main_or_gitonly" has not been set
Property "jd_project_codelet_config_dir" has not been set
Property "project_version_for_jd" has not been set
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s