EVGENIAST / cumulusrdf

Automatically exported from code.google.com/p/cumulusrdf
0 stars 0 forks source link

New (Maven) project layout #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
As discussed here [1], in order to enable several perspectives of the project 
test suite, we should change the project layout a bit. The layout that comes 
from the initial discussion [1] seems something like this:

cumulusrdf
--cumulusrdf-kernel
--cumulusrdf-integration-tests
--cumulusrdf-benchmark
--??

Where 

a) cumulusrdf: a top level project with pom packaging
b) cumulusrdf-kernel: please suggest a more appropriate name :), this is the 
current cumulusrdf module (war packaging). It includes sources and unit tests.
c) cumulusrdf-integration-tests: as the name suggests, this module includes 
only integration / system tests
d) cumulusrdf-benchmark: a special test module dedicated to benchmarking the 
corresponding release artifact

Another interesting module could be a "distribution", that uses the maven 
assembly plugin to produce different kind of artifacts (e.g. onejar, war, 
directory)

[1] 
https://groups.google.com/forum/#!topicsearchin/cumulusrdf-dev-list/maven|sort:d
ate|spell:true/cumulusrdf-dev-list/z3JegSK17gY

Original issue reported on code.google.com by a.gazzarini@gmail.com on 16 Feb 2014 at 4:15

GoogleCodeExporter commented 8 years ago
I think we should also add a 

--cumulusrdf-cli

which only features the CLIs. This way, we could simply add:

<packaging>jar</packaging>

to its pom.xml.

Original comment by andreas.josef.wagner on 11 Mar 2014 at 11:18

GoogleCodeExporter commented 8 years ago
Absolutely +1

2014-03-11 12:18 GMT+01:00 <cumulusrdf@googlecode.com>:

Original comment by a.gazzarini@gmail.com on 11 Mar 2014 at 11:22

GoogleCodeExporter commented 8 years ago

Original comment by a.gazzarini@gmail.com on 25 Mar 2014 at 9:41