| Summary: | Maven Dependencies classpath container does not show up | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Ulli Hafner <Knut.Friedhelm> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | igor |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Ulli Hafner
As far as I can tell, jenkins-core project uses non-standard java compiler and is not supported out-of-the-box by m2e. Please contact us on m2e-dev@eclipse.org list if you are interested to develop such support. Hmm, this did work with all previous versions of m2e. And I don't think that Jenkins/Hudsons requires a different compiler than javac. I think this is a regression in m2e. Do "mvn help:effective-pom" and check if maven-compiler-plugin is bound to any build phase. I made some changes to AbstractJavaProjectConfigurator to allow customization of compiler plugin groupId, artifactId and goal names. It should be possible to develop m2e extension to support alternative (i.e. forked) maven-compiler-plugin implementations relatively easily now. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=c0e3be615997a389f62a64909b5ad3b252a393ca as far as I understand Jenkins does not use custom compiler plugin any more, so more work is planned here. |