[#SES-705] Published Maven POMs don't specify versions for the dependencies

Issue Details [XML]

Key:	SES-705
Type:	Bug
Status:	Open
Priority:	Major
Assignee:	Arjohn Kampman
Reporter:	Nick Giles
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

Sesame

Published Maven POMs don't specify versions for the dependencies

Created: 05/Mar/10 01:01 PM Updated: 12/Apr/10 09:09 PM

Component/s:

None

Affects Version/s:

2.3.1

Fix Version/s:

None

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-spring:pom: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

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Arjohn Kampman [12/Apr/10 09:09 PM]

Could it be that you are using an "older" maven version that doesn't support the import scope yet? Sesame uses the import scope to import a number of dependency declarations from other projects. You'll need maven 2.0.9 or newer to build.