You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2011/08/29 20:31:33 UTC
[jira] Closed: (MCOMPILER-145) Compiler:
${non-existent} resolved as "null", should emit a
warning.
[ https://jira.codehaus.org/browse/MCOMPILER-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MCOMPILER-145.
------------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
Such expressions are resolved by Maven, not by the plugin. For the plugin it is not possible to determine if the value contained an expression or not, it just gets the resolved value.
> Compiler: <executable>${non-existent}</executable> resolved as "null", should emit a warning.
> ---------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-145
> URL: https://jira.codehaus.org/browse/MCOMPILER-145
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Reporter: Ondrej Zizka
> Assignee: Robert Scholte
> Priority: Trivial
>
> When having the following in a profile,
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>1.6</source>
> <target>1.6</target>
> <compilerVersion>1.6</compilerVersion>
> <executable>${jdk16_home}/bin/javac</executable>
> <fork>true</fork>
> <verbose>true</verbose>
> </configuration>
> </plugin>
> the build with ${jdk16_home} not set would fail with:
> Embedded error: Error while executing the external compiler.
> java.io.IOException: null/bin/javac: not found
> I think that the unresolved property should emit a warning rather than being converted to "null" since that is harder to track the issue down that way.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira