Ok, here's the issue:
http://jira.codehaus.org/browse/MNG-3834
It's a pretty simple fix, so I should be able to apply it in maven 2.0.x without
any problems.
It was missing the dependency version, so the error message is correct, but the
message doesn't distinguish between dependencies with or without a classifier.
So the error message could be more clear.
Scott Stark wrote:
So can you create a maven issue to actually list the cause of these
pom
validations errors? The error here is missing the classifier of the
actual dependency.
Paul Gier wrote:
> This should be fixed now. The trunk/pom.xml was missing the
> dependency on jmx-invoker-adaptor-client.
>
> Scott Stark wrote:
>> Trying to compile the jbossas mvn build from the trunk, its failing
>> with:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error building POM (may not be this project's POM).
>>
>>
>> Project ID: org.jboss.jbossas:jboss-as-client
>> POM Location: /home/svn/JBossHead/jboss-head/client/pom.xml
>> Validation Messages:
>>
>> [0] 'dependencies.dependency.version' is missing for
>> org.jboss.jbossas:jboss-as-server
>>
>>
>> Reason: Failed to validate POM for project
>> org.jboss.jbossas:jboss-as-client at
>> /home/svn/JBossHead/jboss-head/client/pom.xml
>>
>>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development