:
Sent: Tuesday, December 20, 2011 11:55 AM
Subject: Re: basic decisions - package and class naming
Social API:
org.apache.deltaspike.social.* +1
the implementation
org.apache.deltaspike.social.impl.* +0 (we don't have this in Seam
and have
the distinction in module name, but it's
: basic decisions - package and class naming
Social API:
org.apache.deltaspike.social.* +1
the implementation
org.apache.deltaspike.social.impl.* +0 (we don't have this in Seam and
have
the distinction in module name, but it's not a big deal for me)
@SPI = +0 I'm not sure to use it but why
,
strub
- Original Message -
From: Antoine Sabot-Durand anto...@sabot-durand.net
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Tuesday, December 20, 2011 11:55 AM
Subject: Re: basic decisions - package and class naming
Social API:
org.apache.deltaspike.social.* +1
Subject: Re: basic decisions - package and class naming
Social API:
org.apache.deltaspike.social.* +1
the implementation
org.apache.deltaspike.social.impl.* +0 (we don't have this in Seam and have
the distinction in module name, but it's not a big deal for me)
@SPI = +0 I'm not sure
?
LieGrue,
strub
- Original Message -
From: Jason Porter lightguard...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Monday, December 12, 2011 7:21 PM
Subject: Re: basic decisions - package and class naming
I'm good for the package naming, include the JSF split, if we're
