maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] (MPH-90) help:effective-pom does not show full effective-pom
Date Thu, 31 Jan 2013 21:20:13 GMT


Robert Scholte commented on MPH-90:

No problem that it is reopened.

I'm not interested in what the debugger is saying halfway the execution, but I'm more interested
in what kind of output you would expect. Please check out this project and run {{mvn clean
verify -Prun-its -Dinvoker.test=effective-pom_properties}} and have a look at the {{target/it/effective-pom_properties/build.log}}.

If you change the {{invoker.goals}} to {{compile}} you'll see something like 
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile from
plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-compiler-plugin:2.3.2, parent:
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile' with
basic configurator -->
[DEBUG]   (f) basedir = E:\java-workspace\apache-maven-plugins\maven-help-plugin\target\it\effective-pom_properties
[DEBUG]   (f) buildDirectory = E:\java-workspace\apache-maven-plugins\maven-help-plugin\target\it\effective-pom_properties\target
[DEBUG]   (f) classpathElements = [E:\java-workspace\apache-maven-plugins\maven-help-plugin\target\it\effective-pom_properties\target\classes]
[DEBUG]   (f) compileSourceRoots = [E:\java-workspace\apache-maven-plugins\maven-help-plugin\target\it\effective-pom_properties\src\main\java]
[DEBUG]   (f) compilerId = javac
[DEBUG]   (f) debug = true
[DEBUG]   (f) failOnError = true
[DEBUG]   (f) fork = false
[DEBUG]   (f) generatedSourcesDirectory = E:\java-workspace\apache-maven-plugins\maven-help-plugin\target\it\effective-pom_properties\target\generated-sources\annotations
[DEBUG]   (f) optimize = false
[DEBUG]   (f) outputDirectory = E:\java-workspace\apache-maven-plugins\maven-help-plugin\target\it\effective-pom_properties\target\classes
[DEBUG]   (f) outputFileName = mph-90-1.0-SNAPSHOT
[DEBUG]   (f) projectArtifact =
[DEBUG]   (f) session = org.apache.maven.execution.MavenSession@2bbd9de3
[DEBUG]   (f) showDeprecation = false
[DEBUG]   (f) showWarnings = false
[DEBUG]   (f) source = 1.6
[DEBUG]   (f) staleMillis = 0
[DEBUG]   (f) target = 1.6
[DEBUG]   (f) verbose = false
[DEBUG] -- end configuration --

IMO {{effective-pom}} is not about the build-plan and build-configuration, but only about
merging the current pom with all its parent up to the super-pom provided by Maven.
> help:effective-pom does not show full effective-pom
> ---------------------------------------------------
>                 Key: MPH-90
>                 URL:
>             Project: Maven 2.x Help Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>         Environment: Maven 2.2.1 and Maven 3.0.3
>            Reporter: Michael Osipov
>            Assignee: Robert Scholte
>         Attachments: compiler-debug.png, effective-pom.log, pom.xml, target-option.png
> When I define something like this in my POM:
> {code:xml}
> <properties>
>   <maven.compiler.source>1.6</maven.compiler.source>
>   <>1.6</>
> </properties>
> {code}
> the compiler plugin picks this up but this settings is not reflected in the {{Model}}
and not written out as part of the effective POM.
> Either this is fixed within the system or the docs of this plugin need to mention this
> This is related to MJAVADOC-310 and MPIR-263.
> I a workaround for now by passing those properties to the plugin but this does not solve
this problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message