Do you mean that you are creating jar files with a manifest containing for
instance Main-Class: ${mainclass} instead of Main-Class: com.some
company.SomeApp ?
Ant does not enforce that properties be set before they are used. When an ant
task is invoked with the place holder ${someproperty} and s
Sorry for the incomplete sentences. It's hard to see what I've typed,
especially when every application uses slightly dark fonts on a slightly
lighter background, so by the time I get to the end of a long sentence, it
sometimes sounds rambling. Anyway, what I meant to say is that when I asked
It turns out I'm not the only one here who simply modifies existing build
files, although I have managed to exclude descendants of an included fileset
dir attribute. When I asked why a non-existent Main-Class value wouldn't
generate an error and, at least on one installation, still allow the co
