• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Do we need to build directory structure in source directory?

 
Holmes Wong
Ranch Hand
Posts: 163
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I have a source directory which contains all source files, I am wondering if we need to
build a directory structure following that of
object files? If we have three packages in source
directory, then, it seems it will be really hard to use javadoc to create doc files. Any comments?
 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

... it seems it will be really hard to use javadoc to create doc files

Not hard at all. Just specify path to source and path to classes, and javadoc utility will find your source. For example:

Eugene.
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well I just had the .class files and .java files in the same directories.
I didn't seperate the source from the compiled class. Then my javadoc command was a simple line.
javadoc -private suncertify.db suncertify.client suncertify.help
Now in real life it is more maintainable to seperate the source from compiled.
Mark
 
Holmes Wong
Ranch Hand
Posts: 163
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks, guys.
Mark, why do we need to expose our private
members? I only showed public and protected
members.
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just liked to show private too. I like that they show the private in Java's API docs, so I just followed that. I don't think it really matters.
Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic