>> The downstream user must not be confused and really be aware of that it is >> not an endorsed Apache release.
> We are definitely compliant with the first two issues. The last one is a bit > vague, but it implies that we could be compliant simply by including > "incubating" in the version we include in the JAR's manifest... Unfortunately, I think just having it in the JAR's manifest wouldn't suffice, because downstream users won't go looking in there to see what we included. Simply looking at the filename could give them the impression that we're an endorsed apache release, which means we'll have broken the intent of the law, if not the letter of the law. -T
