Since we always release all of DeltaSpike in one go, the versions are always
the same. This is really convenient to just add a property
properties
deltaspike.version0.1-SNAPSHOT/deltaspike.version
/properties
and use that for all your project.
LieGrue,
strub
lightguard
On Thu, Dec 15, 2011 at 02:52, Gerhard Petracek
gerhard.petra...@gmail.comwrote:
hi @ all,
since we have started several discussions, it makes sense to prototype some
parts immediately.
mark and i suggest to start at [1] while the infra team is preparing our
repository, ldap
On Thu, Dec 15, 2011 at 3:31 PM, Mark Struberg strub...@yahoo.de wrote:
Well, we are now hitting the wall - so we need a resolution asap.
For the core module we would have
for core-api:
org.apache.deltaspike.core. ?
for core-impl:
org.apache.deltaspike.core.impl. ?
yes!
And/or
hi @ all,
i created [1] for collecting the suggestions.
if you don't like one of the mentioned conventions, add your own suggestion.
i'll start a vote about it on monday.
regards,
gerhard
[1] https://issues.apache.org/jira/browse/DELTASPIKE-12
2011/12/12 Jason Porter lightguard...@gmail.com
On Mon, Dec 12, 2011 at 12:37 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
I'm a fan of a pretty tight coding convention observation even at build time.
What we usually have (in owb and myfaces) is an own 'buildtools' project
which contains the checkstyle rules as own artifact.
This will
On Mon, Dec 12, 2011 at 1:38 PM, Gerhard Petracek gpetra...@apache.org wrote:
+1 for 4 spaces
yup
regards,
gerhard
2011/12/12 Shane Bryzak sbry...@gmail.com
On Mon, Dec 12, 2011 at 9:37 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
I'm a fan of a pretty tight coding convention
imo whitespace is a must, it helps with readability. I'm fine with
everything else
On Thu, Dec 15, 2011 at 14:02, Matthias Wessendorf mat...@apache.orgwrote:
5) a space between keyword and round bracket (e.g. if (...) instead of
if(...))
6) a space before and after an operand (e.g. a = 1 +
at [1] i summarized what we have agreed on so far.
- let's continue with the util methods.
suggestions for the util methods:
public T T getContextualReferenceByClass(ClassT type, boolean
optionalBeanAllowed, Annotation... qualifiers)
public T T getContextualReferenceByName(String name,
boolean
Shane's probably tired of hearing me harp on docbook, oh well :)
Here's a tool that's nice to use, output is good and it has a great
community following: http://sphinx.pocoo.org/ If we want to look into it,
great, if we go back to docbook, great, I'll stop complaining and just use
it.
Buildable
