You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/08/12 23:59:57 UTC
[jira] Closed: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
[ http://jira.codehaus.org/browse/MNG-675?page=all ]
John Casey closed MNG-675:
--------------------------
Assign To: John Casey
Resolution: Fixed
added formatting for the dependency instance alongside those particular validations...also it1013 to express this behavior.
> Improve 'dependencies.dependency.version is missing' error message
> ------------------------------------------------------------------
>
> Key: MNG-675
> URL: http://jira.codehaus.org/browse/MNG-675
> Project: Maven 2
> Type: Improvement
> Reporter: Kenney Westerhof
> Assignee: John Casey
> Fix For: 2.0-beta-2
>
>
> When leaving out a <version> from at least one dependency, the following
> error message appears. With a lot of dependencies, where all versions are managed
> in dependencyManagement in the parent pom, it's hard to tell which version is missing:
> [INFO] BUILD FAILURE
> [INFO] ----------------------------------------------------------------------------
> [INFO] Reason: Failed to validate POM for 'm:\qwesken_adm_1.0_dev_inc2\spf\products\adm\design\application\pom.xml'.
> Reason(s):
> [0] 'dependencies.dependency.version' is missing.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org