Clearing the target directory did the trick.  

Although I updated the project to only use AOT-compiled classes when 
building the uberjar, the leiningen alias I created to "build-all" was 
building the uberjar before generating docs.  So by the time the docs were 
being generated, the target directory already had AOT-compiled classes in 
it, which was the root cause of the namespace docstrings not working.  

I re-ordered the commands in the "build-all" alias so docs get generated 
before the uberjar.  

For those that are interested here is the alias as defined in the leiningen 
project.clj file.
"rebuild-all" ["do"  ["sub" "clean"] ["sub" "jar"] ["sub" "install"] 
["clean"] ["jar"] ["doc"] ["marg"] ["uberjar"]]
*note* The sub plugin is extremely useful when managing project 
dependencies.


The Codox generated documentation is correct now.

Interestingly enough, more classes then I expected were being 
AOT-compiled.... 

Thanks,
On Wednesday, December 17, 2014 9:10:10 AM UTC-5, James Reeves wrote:
>
> Have you tried clearing your target directory? If there are some 
> AOT-compiled class files in there, they lack the metadata that Codox needs 
> to generate the docs.
>
> - James
>
> On 16 December 2014 at 17:02, Nick Gonzalez <nickmg...@gmail.com 
> <javascript:>> wrote:
>
>> I'm using codox to generate api documentation for a fairly large Cojure 
>> project, and it is ignoring namespace doc strings for all but some of my 
>> namespaces.  i have moved the :aot directives into the uberjar profile, so 
>> the :apt option should not be the problem.  but who knows.  
>>
>> 1. Has anyone else experienced this issue?  
>> 2. Is there a better way to generate API docs?
>>
>> FYI - I am also using Marginalia, and it is working great.  There are no 
>> missing doc strings in the output.
>>
>> Thanks,
>> -NG
>>
>>
>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@googlegroups.com 
>> <javascript:>
>> Note that posts from new members are moderated - please be patient with 
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+u...@googlegroups.com <javascript:>
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to clojure+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to