Hi folks!

Welcome on board fellow CDI geeks!

I'd like to discuss how we kick off the work (the first steps are always the 
hardest).

1.)
Since we will get 1 git repo for the start, and since with using git, it's 
almost the most important part at all, I'd like to start the discussion with 
how we slice the cake.
Means which directory structure we like to use for the project layout.

I wrote up a first proposal into our official Wiki
https://cwiki.apache.org/confluence/display/DeltaSpike/Project+Structure

2.)
We need to discuss which artifacts we produce.
So far we had good results with api+impl (+optional spi?) for each 'area' and 
bundle them together at a later stage with the maven-shade-plugin.

3.) 
Which 'areas' or modules do we like to forsee?
Current suggestion is to split those based on their dependencies. A user shall 
not be forced to add some library to his project which he isn't going to use. 
E.g. it should not be required to add javax.faces-api for writing a pure JavaSE 
project. Thus the following candidates exist:
* core
* jsf12
* jsf20
* jpa

How do we treat future CDI-1.0 vs CDI-1.1 changes?


4.)
How we do our documentation.


We might finally split up the discussion in single mail threads, but I like to 
kick off the think process at least ;)

LieGrue,
strub

Reply via email to