[
http://jira.codehaus.org/browse/MNG-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192731#action_192731
]
Anders Kr. Andersen commented on MNG-4383:
------------------------------------------
Hi Paul
Yes it seems to be an error here.
On the other hand expression language is always like that. If the variable
cannot be looked up in the map, the variable key is printed.
I find it relative problematic to start evaluating the importance of a missing
key.
Here an exception could be nice, but many other places ... and the way EL works
in general .. it would be the key you will see.
So I think that ${xxxxx} is the error message you will get. So this is really
not an error, but a feature
/Anders Kr.
> Uninterpolated expressions should cause an error
> ------------------------------------------------
>
> Key: MNG-4383
> URL: http://jira.codehaus.org/browse/MNG-4383
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.2.1, 3.0-alpha-2
> Reporter: Paul Benedict
>
> I declared a dependency as such:
> {noformat}<dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>${slf4j.version}</version>
> </dependency>{noformat}
> But did not define the *slf4j.version* property. Obviously ${...} is an
> expression and if the expression is not resolved, why allow it? Here was the
> output:
> {noformat} Downloading:
> http://repo1.maven.org/maven2/org/slf4j/slf4j-api/${slf4j.version}/slf4j-api-${slf4j.version}.pom{noformat}
>
> In terms of usability, an obvious expression should be interpolated. If it
> cannot, it should be a runtime error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
