[#SES-222] Split Sesame into separate functional modules

Issue Details [XML]

Key:	SES-222
Type:	Task
Status:	Resolved
Resolution:	Fixed
Priority:	Major
Assignee:	Arjohn Kampman
Reporter:	Jeen Broekstra
Votes:	0
Watchers:	0

Operations

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

Sesame

Split Sesame into separate functional modules

Created: 23/Jan/06 02:35 PM Updated: 02/Nov/06 05:20 PM

Component/s:

None

Affects Version/s:

2.0-alpha-2

Fix Version/s:

2.0-alpha-4

Issue Links:

Dependency

This issue depends on:
	~~SES-301~~ Configurable/extensible RDF parsers a...
	~~SES-302~~ Configurable/extensible query languag...
	~~SES-303~~ Configurable/extensible query result ...

Duplicate

This issue is duplicated by:
	~~SES-306~~ Sesame API's are inter-dependent; it ...

Description

The current development/distribution strategy of Sesame is too monolithic. We plan to enable releases of Sesame where the core components and storage backends are released individually. This will likely mean that the native store and any RDBMS stores are developed in separate modules. The memory store /might/ also be moved to a separate module.

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Arjohn Kampman [12/Jun/06 04:13 PM]

Apache maven offers a nice infrastructure for handling code that has been split into separate modules (among other things): http://maven.apache.org/

[ Permlink ]

Comment by Arjohn Kampman [20/Sep/06 11:55 AM]

Sesame 2 has moved from ant to maven2 as the primary build system. The code is now partly distributed over several modules. Goal is to create a module for each major API and separate modules for each implementation of these APIs. The result will be a much more configurable and extensible RDF framework.