Snapshot of the current truck would be fine. Not sure where that link would be documented. I assume the staging is a temp location. This link looks like all Javadoc I've seen, so it's fine from my point of view.
> Technically, javadocs are available in maven central [1] for each release. > But I think it's just convenient to have it hosted online for > browsing/searching. I did not know that. I agree. Hosted ones are so much more, umm, instantly available. > I think the key would be to point new users to the Type System and the > different "Types" that are available from cTAKES. I don't understand the question. Is it related to the Javadoc? Interestingly the Javadoc shows that one package still has "edu.mayo.bmi". Was that missed? Thanks Troy -----Original Message----- From: dev-return-1480-Bleeker.Troy=mayo....@ctakes.apache.org [mailto:dev-return-1480-Bleeker.Troy=mayo....@ctakes.apache.org] On Behalf Of Chen, Pei Sent: Tuesday, April 09, 2013 11:47 AM To: dev@ctakes.apache.org Subject: RE: Apache cTAKES javadocs Hi Troy, I generated the javadocs for 3.0.0 on the site: Preview in staging http://ctakes.staging.apache.org/apidocs/3.0.0/ Probably a good idea to keep both a snapshot of trunk as the individual releases? I think the key would be to point new users to the Type System and the different "Types" that are available from cTAKES. What do you think? Note: Technically, javadocs are available in maven central [1] for each release. But I think it's just convenient to have it hosted online for browsing/searching. --Pei [1] http://search.maven.org/#search%7Cga%7C1%7Cctakes > -----Original Message----- > From: Bleeker, Troy C. [mailto:bleeker.t...@mayo.edu] > Sent: Monday, April 08, 2013 5:38 PM > To: dev@ctakes.apache.org > Subject: RE: Apache cTAKES javadocs > > Cool! The Javadocs should be tied to a release so any developer could > look up the Javadocs that goes with what they have installed. Given > that you could have a URL that points to a certain release, then I > think we should add it to: > > - As a bullet here: http://ctakes.apache.org/developerguide.html > - In the documentation box for 3.0 archive here: > http://ctakes.apache.org/roadmap.html > - The developer doc could use an optional section on incorporating the > Javadoc into an Eclipse environment: > https://cwiki.apache.org/confluence/display/CTAKES/cTAKES+3.0+Develope > r+Install+Guide > > Thanks > Troy > -----Original Message----- > From: dev-return-1469-Bleeker.Troy=mayo....@ctakes.apache.org > [mailto:dev-return-1469-Bleeker.Troy=mayo....@ctakes.apache.org] On > Behalf Of Chen, Pei > Sent: Monday, April 08, 2013 3:16 PM > To: dev@ctakes.apache.org > Subject: Apache cTAKES javadocs > > In the spirit of making it easier for new developers, as Tim pointed > out earlier, I think it would be useful to point users to more info on > exactly what they can get out of cTAKES(API). > Even though most of the driving Annotators are just .process(jCas), I > think it will useful to also reference them to mainly the > org.apache.ctakes.typesystem.* (essentially, what they can extract out > of cTAKES programmatically after the pipeline has been completed.) > > Preview at staging area: > http://ctakes.staging.apache.org/apidocs/trunk/ > [I generated it based off the latest head revision] > > Any preference as to where to put this link on the homepage (Troy? :))? > > --Pei >
