[jira] [Created] (DELTASPIKE-213) move atinject-api, jcdi-api and interceptors-api dependencies to the container configuration

Mark Struberg created DELTASPIKE-213: Summary: move atinject-api, jcdi-api and interceptors-api dependencies to the container configuration Key: DELTASPIKE-213 URL:

[jira] [Commented] (DELTASPIKE-213) move atinject-api, jcdi-api and interceptors-api dependencies to the container configuration

[ https://issues.apache.org/jira/browse/DELTASPIKE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403723#comment-13403723 ] Mark Struberg commented on DELTASPIKE-213: -- I've now moved those API jars to

Re: Sandbox for DeltaSpike

Hello, so late introduction from myself :) I live in Poland - Warsaw area - and work remotely from there. On the professional side since quite a few years focused on JEE portals. Currently I'm the GateIn Portal Project Lead [0] and Platform Architect of corresponding RedHat product offering

Re: [suggestion] - Documentation

Hi Charles! Ok, I should have been more clear :) That's because you are not yet a committer on DeltaSpike, right? This all works via SVN rights, but the CMS documentation also has a section about providing a kind of svn diff and ship it as patch afterwards. This is done to get rid of the

Re: Sandbox for DeltaSpike

Hi Bolek, welcome on board! I think a bit too much 'noise' is much better than too less information on the list. One of the core principals of the ASF is 'community for code'. The best source is almost useless if there is no community around. Thus one of the most important stuff at the ASF is

Re: [suggestion] - Documentation

I'm not still a committer. So let's go for the patches On Fri, Jun 29, 2012 at 12:37 PM, Mark Struberg [via Apache DeltaSpike Incubator Discussions] ml-node+s2316169n4652906...@n4.nabble.com wrote: Hi Charles! Ok, I should have been more clear :) That's because you are not yet a

Re: Sandbox for DeltaSpike

I think it is a good idea. Discussions can and should take place, but IMO an opend sandbox would be a good place to stage code for new features without endangering the stability of the whole project. On 12-06-26 3:39 PM, Jason Porter wrote: Hey everyone! I wanted to bring up the idea of

Re: [seam-dev] Sandbox for DeltaSpike

I see nothing wrong with a sandbox, particularly since I think sometimes seeing code is a better way to make spark discussion than trying to discuss everything up front. In order to facilitate contribution and individual communication styles, and to promote more contributions in general, I think

Re: Enable Examples in our build by default

+1 they should be built! On Thu, Jun 28, 2012 at 1:17 PM, Jason Porter lightguard...@gmail.comwrote: +1 to building them On Wed, Jun 13, 2012 at 3:10 AM, Mark Struberg strub...@yahoo.de wrote: Hi! Why are our examples not in our build atm? We shall not deploy them, but building them

Re: [VOTE] Converter framework

txs folks, I already dropped them. Converter frameworks per se is a good idea. But DS is just not the right place it seems. LieGrue, strub - Original Message - From: Lincoln Baxter, III lincolnbax...@gmail.com To: deltaspike-dev@incubator.apache.org Cc: Sent: Friday, June 29,

Re: [VOTE] Converter framework

I think it's something we can revisit later once we have more core functionality working :) On Fri, Jun 29, 2012 at 3:31 PM, Mark Struberg strub...@yahoo.de wrote: txs folks, I already dropped them. Converter frameworks per se is a good idea. But DS is just not the right place it seems.