: The the "bad" java doc will be removed soon as I almost finished the
: Gdata Object Model which means the google client classes are not
The problems Grant was having actually had nothing to do with gdata ... it
was trggered by some core code that uses assertions -- something perfectly
valid in
yep, that works. I will commit the change.
On Dec 12, 2006, at 2:50 PM, Chris Hostetter wrote:
: OK, if I put in source="1.4" then it works, but is that going to
: break the GData stuff?
try adding this to the javadoc task...
source="${ant.java.version}"
...the gdata stuff is au
Thanks hoss for the answer
The the "bad" java doc will be removed soon as I almost finished the
Gdata Object Model which means the google client classes are not
needed anymore. I will change the structure of the gdata contrib
project tomorrow which will cause some commits. I will skip rhe
int
: OK, if I put in source="1.4" then it works, but is that going to
: break the GData stuff?
try adding this to the javadoc task...
source="${ant.java.version}"
...the gdata stuff is automatically skiped when the java version running
ant isn't 1.5, and with that option the javadocs se
OK, if I put in source="1.4" then it works, but is that going to
break the GData stuff?
On Dec 12, 2006, at 9:38 AM, Michael McCandless wrote:
Grant Ingersoll wrote:
Can anyone recreate this:
With JDK 1.4:
I run ant javadocs and I get no output whatsoever in build/docs/api
I see this as w
Grant Ingersoll wrote:
Can anyone recreate this:
With JDK 1.4:
I run ant javadocs and I get no output whatsoever in build/docs/api
I see this as well, with Sun JDK 1.4.2 on Windows, ant 1.6.5. If I move
that one source
(src/java/org/apache/lucene/search/spans/NearSpansOrdered.java)
out of t
