javac option to compile all java files under a given directory recursively

Question

I am using the javac compiler to compile java files in my project  The files are distributed over several packages like this  com vistas util  com vistas converter  com vistas LineHelper  com current mdcontect   Each of these packages has several java files  I am using javac like this   javac com vistas util   java com vistas converter   java       com vistas LineHelper   java com current mdcontect   java    in one line   Instead of giving so many paths  how can I ask the compiler to compile recursively all the java files from the parent com directory

User · Answer

find   -name    java  -print   xargs javac    Kinda brutal  but works like hell   Use only on small programs  it s absolutely not efficient

User · Answer

I would advice you to learn using ant  which is very-well suited for this task and is very easy to grasp and well documented   You would just have to define a target like this in the build xml file    lt target name  compile  gt       lt javac srcdir  your source directory             destdir  your output directory             classpath  xyz jar    gt   lt  target gt

User · Answer

In the usual case where you want to compile your whole project you can simply supply javac with your main class and let it compile all required dependencies   javac -sourcepath   path to Main java

User · Answer

I m just using make with a simple makefile that looks like this   JAVAC   javac -Xlint unchecked sources     shell find   -type f -name    java   classes     sources  java  class   all     classes   clean           rm -f   classes     class     java           JAVAC    lt    It compiles the sources one at a time and only recompiles if necessary

User · Answer

I ve been using this in an Xcode JNI project to recursively build my test classes   find   PROJECT DIR  -name    java  -print   xargs javac -g -classpath   BUILT PRODUCTS DIR  -d   BUILT PRODUCTS DIR

User · Answer

javac -cp  jar path      find   -name    java     I prefer not to use xargs because it can split them up and run javac multiple times  each with a subset of java files  some of which may import other ones not specified on the same javac command line   If you have an App java entrypoint  freaker s way with -sourcepath is best  It compiles every other java file it needs  following the import-dependencies  eg   javac -cp  jar path    -sourcepath src  src com companyname modulename App java  You can also specify a target class-file dir  -d target

User · Answer

javac command does not follow a recursive compilation process  so you have either specify each directory when running command  or provide a text file with directories you want to include   javac -classpath    CLASSPATH    java sources txt

User · Answer

If your shell supports it  would something like this work     javac com      java    If your shell does not support     then maybe  javac com       java   works  for all packages with 3 components - adapt for more or less

User · Answer

I would also suggest using some kind of build tool  Ant or Maven  Ant is already suggested and is easier to start with  or an IDE that handles the compilation  Eclipse uses incremental compilation with reconciling strategy  and you don t even have to care to press any  quot Compile quot  buttons   Using Javac If you need to try something out for a larger project and don t have any proper build tools nearby  you can always use a small trick that javac offers  the classnames to compile can be specified in a file  You simply have to pass the name of the file to javac with the   prefix  If you can create a list of all the   java files in your project  it s easy    Linux   MacOS   find -name  quot   java quot   gt  sources txt   javac  sources txt     Windows  gt  dir  s  B   java  gt  sources txt  gt  javac  sources txt   The advantage is that is is a quick and easy solution  The drawback is that you have to regenerate the sources txt file each time you create a new source or rename an existing one file which is an easy to forget  thus error-prone  and tiresome task   Using a build tool On the long run it is better to use a tool that was designed to build software  Using Ant If you create a simple build xml file that describes how to build the software   lt project default  quot compile quot  gt       lt target name  quot compile quot  gt           lt mkdir dir  quot bin quot   gt           lt javac srcdir  quot src quot  destdir  quot bin quot   gt       lt  target gt   lt  project gt   you can compile the whole software by running the following command    ant   The advantage is that you are using a standard build tool that is easy to extend  The drawback is that you have to download  set up and learn an additional tool  Note that most of the IDEs  like NetBeans and Eclipse  offer great support for writing build files so you don t have to download anything in this case   Using Maven Maven is not that trivial to set up and work with  but learning it pays well  Here s a great tutorial to start a project within 5 minutes   It s main advantage  for me  is that it handles dependencies too  so you won t need to download any more Jar files and manage them by hand and I found it more useful for building  packaging and testing larger projects  The drawback is that it has a steep learning curve  and if Maven plugins like to suppress errors  -  Another thing is that quite a lot of tools also operate with Maven repositories  like Sbt for Scala  Ivy for Ant  Graddle for Groovy    Using an IDE Now that what could boost your development productivity  There are a few open source alternatives  like Eclipse and NetBeans  I prefer the former  and even commercial ones  like IntelliJ  which are quite popular and powerful  They can manage the project building in the background so you don t have to deal with all the command line stuff  However  it always comes handy if you know what actually happens in the background so you can hunt down occasional errors like a ClassNotFoundException  One additional note For larger projects  it is always advised to use an IDE and a build tool  The former boosts your productivity  while the latter makes it possible to use different IDEs with the project  e g   Maven can generate Eclipse project descriptors with a simple mvn eclipse eclipse command   Moreover  having a project that can be tested built with a single line command is easy to introduce to new colleagues and into a continuous integration server for example  Piece of cake  -

[java] javac option to compile all java files under a given directory recursively

Examples related to java

Examples related to javac