deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Wessendorf <mat...@apache.org>
Subject Re: First steps
Date Fri, 09 Dec 2011 12:01:56 GMT
lol

I mean the 'api' w/in the api - which is IMO awful

Sent from my iPhone

On 09.12.2011, at 12:52, Gerhard Petracek <gerhard.petracek@gmail.com> wrote:

> hi matthias,
>
> myfaces extcdi (aka codi) is a sub-project. -> with deltaspike we have a
> different situation. -> there won't be that long package names.
>
> regards,
> gerhard
>
> http://www.irian.at
>
> Your JSF/JavaEE powerhouse -
> JavaEE Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
>
> 2011/12/9 Matthias Wessendorf <matzew@apache.org>
>
>> re #3:
>>
>> please let's avoid awful package names like:
>>
>> http://svn.apache.org/repos/asf/myfaces/extensions/cdi/trunk/jee-modules/jpa-module/api/src/main/java/org/apache/myfaces/extensions/cdi/jpa/api/
>>
>> thx,
>> Matthias
>>
>> On Fri, Dec 9, 2011 at 11:49 AM, Gerhard Petracek
>> <gerhard.petracek@gmail.com> wrote:
>>> hi @ all,
>>>
>>> @#1:
>>> +1 for the basic idea
>>>
>>> @#2:
>>> +1 for api + impl.
>>> @separated spi module: +0
>>>
>>> @#3
>>> +1
>>> @versions of cdi: at myfaces the latest spec. version is used in the
>>> trunk and all previous versions are branches. since that works pretty
>> well,
>>> +1 for handling it that way (for sure with the corresponding concepts of
>>> git).
>>>
>>> @#4
>>> at least for our reports,... we have a confluence space[1].
>>>
>>> regards,
>>> gerhard
>>>
>>> [1] http://cwiki.apache.org/confluence/display/DeltaSpike
>>>
>>>
>>>
>>> http://www.irian.at
>>>
>>> Your JSF/JavaEE powerhouse -
>>> JavaEE Consulting, Development and
>>> Courses in English and German
>>>
>>> Professional Support for Apache MyFaces
>>>
>>>
>>>
>>> 2011/12/9 Mark Struberg <struberg@yahoo.de>
>>>
>>>> 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
>>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>

Mime
View raw message