Update the "non-javac-compilers" guide and add an integration test. #937
Conversation
|
Hi, will have a look in the next days or next weekend. Modt prob during the next days, when at an unconference. |
| <configuration> | ||
| <compilerId>eclipse</compilerId> | ||
| <compilerId>ecj</compilerId> | ||
| <!-- TODO: remove source and target after we identified where Maven inherits those values. --> |
There was a problem hiding this comment.
Suggest to create an issue for this, so it's more visible
| public static void main(final String[] args) { | ||
| String dummy = new Integer(1); | ||
| System.out.println("Hi!"); |
| Currently, the Compiler Plugin is bundled with the <<<javac>>> compiler | ||
| with artifactId <<<plexus-compiler-javac>>> version <<${plexusCompilerVersion}>>, | ||
| which can be seen as one of the dependencies declared inside the Compiler Plugin's POM. | ||
| By default, the Compiler Plugin uses the <<<javac>>> compiler |
There was a problem hiding this comment.
| By default, the Compiler Plugin uses the <<<javac>>> compiler | |
| By default, the Maven Compiler Plugin uses the <<<javac>>> compiler |
| which can be seen as one of the dependencies declared inside the Compiler Plugin's POM. | ||
| By default, the Compiler Plugin uses the <<<javac>>> compiler | ||
| bundled in the <<<javax.tools>>> package of the standard Java library. | ||
| But it is possible to use any other implementation, provided that the |
There was a problem hiding this comment.
Reads bumby, maybe this is a little less rocky?
But it is possible to use any other compiler, as long the implementation declares itself as a ....
| bundled in the <<<javax.tools>>> package of the standard Java library. | ||
| But it is possible to use any other implementation, provided that the | ||
| implementation declares itself as a <<<javax.tools.JavaCompiler>>> service. | ||
| For using such implementation: |
There was a problem hiding this comment.
| For using such implementation: | |
| To use such an implementation: |
| dependency when declaring the plugin in your project's <<<pom.xml>>>. The example | ||
| below shows how to use the <<<csharp>>> compiler: | ||
| The example below shows how to use the Eclipse compiler <<<ecj>>>. | ||
| Note that at the contrary of Maven 3, there is no Plexus dependency to add. |
There was a problem hiding this comment.
Why does Plexus pops up here?
There was a problem hiding this comment.
In Maven 3, it was necessary to add two dependencies:
- The Eclipse compiler
- A Plexus extension which was a wrapper around the Eclipse compiler.
Actually, the Plexus extension had the Eclipse compiler as a transitive dependency, so it may look as a single dependency in the pom.xml.
In Maven 4, there is no longer wrappers around the various compilers. The Eclipse compiler is used directly (through the standard javax.tools.JavaCompiler interface). I mentioned that in case some users were aware of the use of Plexus as an intermediate API, and were wondering whether Plexus was still needed. But I have no problem in omitting this details if too distracting.
| dependency when declaring the plugin in your project's <<<pom.xml>>>. The example | ||
| below shows how to use the <<<csharp>>> compiler: | ||
| The example below shows how to use the Eclipse compiler <<<ecj>>>. | ||
| Note that at the contrary of Maven 3, there is no Plexus dependency to add. |
There was a problem hiding this comment.
Does this configuration is limited to Maven 3/4 or useable with both? Maybe should be noticed to be clear (esp. as some things are only limit to version 4.
There was a problem hiding this comment.
This configuration (without Plexus) works with the Maven Compiler Plugin 4 only, which itself requires Maven 4.
Fix #904.