Here Maven is using the version of the Java compiler that comes with my local JDK. Maven to do the "real" builds (full test suite, building deployment artifacts etc.).The built-in Eclipse compiler for quick testing (JUnit), debugging and local execution.For example, in all of my Eclipse Java projects I use: with something like Maven) that does not use the Eclipse compiler which is responsible for producing the final deployable artifacts. It would be normal to have a separate build process (e.g. I realize that there may be some outliers out there who DO use ecj in production, but is this generally frowned upon? Or is this normal/accepted practice? Mostly I'm looking for the general convention in the Eclipse/Java community. Is whats produced by Eclipse ever used in production? Or is it typically only used to support Eclipse's features (ie its intellisense/incremental building/etc)? Is it typical that for the final "release" build of a project, that ant, maven, or another tool is used to do the full build from the command line? I'm used to the project being the make file. I've noticed too that many projects come with ant files to build the project that uses the java compiler built into the system for doing the production builds.Ĭoming from a Windows/Visual Studio world where Visual Studio is invoking the compiler for both production and debugging, I'm used to the IDE having a more intimate relationship with the command-line compiler. Eclipse seems to by default output incrementally built class files to the projRoot/bin folder. One of my most recent discoveries was how Eclipse comes shipped with its own java compiler (ejc) for doing incremental builds.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |