You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2005/07/28 12:47:57 UTC
[jira] Created: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
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
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
[jira] Updated: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-675?page=all ]
Trygve Laugstol updated MNG-675:
--------------------------------
Complexity: Novice
> 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
> 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
[jira] Updated: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-675?page=all ]
Brett Porter updated MNG-675:
-----------------------------
Fix Version: 2.0-beta-2
go for it
> 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
> 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
[jira] Commented: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "Jesse McConnell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-675?page=comments#action_44387 ]
Jesse McConnell commented on MNG-675:
-------------------------------------
looks nice now...here is sample output:
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ----------------------------------------------------------------------------
[INFO] Reason: Failed to validate POM for '/home/jesse/src/g-maven/g-app/pom.xml'.
Reason(s):
[0] In Dependency {groupId=gallup.g, artifactId=g-ejbs, version=null, type=jar}:
-> 'dependencies.dependency.version' is missing.
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Fri Aug 12 16:58:38 CDT 2005
[INFO] Final Memory: 1M/40M
[INFO] ----------------------------------------------------------------------------
> 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
[jira] Closed: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-675?page=all ]
Brett Porter closed MNG-675:
----------------------------
Resolution: Fixed
Fix Version: (was: 2.0-beta-2)
2.0-beta-1
> 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-1
>
>
> 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
[jira] Reopened: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-675?page=all ]
Brett Porter reopened MNG-675:
------------------------------
> 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-1
>
>
> 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
[jira] Commented: (MNG-675) Improve 'dependencies.dependency.version is missing' error message
Posted by "Magnus Heino (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-675?page=comments#action_48926 ]
Magnus Heino commented on MNG-675:
----------------------------------
This dependency:
<dependency>
<groupId>batik</groupId>
<artifactId>batik:batik-svggen</artifactId>
<version>1.6</version>
</dependency>
using maven-artifact-ant-2.0-dep.jar will cause the same "Failed to validate POM" without any help error message.
Fix it to :
<dependency>
<groupId>batik</groupId>
<artifactId>batik-svggen</artifactId>
<version>1.6</version>
</dependency>
and it will work just fine...
> 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-1
>
>
> 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