Published Maven POMs don't specify versions for the dependencies

Description

If you use the Aduna Maven repository (http://repo.aduna-software.org/maven2/releases) and pull Sesame artefacts from there, Maven fails to validate the POM files, and thus doesn't resolve the dependencies. Typical error: [WARNING] POM for 'org.openrdf.sesame:sesame-http-server-springom:2.3.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM [DEBUG] Reason: Failed to validate POM [DEBUG] Validation Errors: [DEBUG] 'dependencies.dependency.version' is missing for info.aduna.appbase:aduna-appbase-webapp-base-core [DEBUG] 'dependencies.dependency.version' is missing for info.aduna.commons:aduna-commons-io [DEBUG] 'dependencies.dependency.version' is missing for info.aduna.commons:aduna-commons-webapp-core [DEBUG] 'dependencies.dependency.version' is missing for javax.servlet:servlet-api [DEBUG] 'dependencies.dependency.version' is missing for org.springframework:spring-webmvc

Environment

None

Status

Assignee

Peter Ansell

Reporter

Nick Giles

Labels

None

Fix versions

Affects versions

Priority

Major
Configure