Broken again ;-)
> On 16 Oct 2014, at 14:35, Rafael Benevides wrote:
>
> Fixed!
>
> Thanks
> Em 10/16/14, 9:34, Pete Muir escreveu:
>> The staging URL is broken now.
>>
>> On 15 Oct 2014, at 15:35, Rafael Benevides wrote:
>>
>>> Hi all
The staging URL is broken now.
On 15 Oct 2014, at 15:35, Rafael Benevides wrote:
> Hi all,
>
> I'd like to share a preview (and ask for feedback) of the documentation
> refactoring that is being made by Michelle and her team.
>
> It's not complete yet, but as soon as we have a feedback (and
+1 this is something I’ve heard a lot of people ask for, and will make getting
the word out about DS much easier.
On 7 Sep 2014, at 16:06, John D. Ament wrote:
> Hi all
>
> I was looking at other apache projects and noted that many of them include
> dedicated pages for each release, with some
Looks good to me.
On 28 Aug 2014, at 18:03, Rafael Benevides wrote:
> I believe that the work for the asciidoc documentation is ready!
>
> Please, check this generated asciidcotor page:
> http://deltaspike.apache.org/documentation/container-control-test.html
>
> The branch with the source cod
On 7 Aug 2014, at 18:47, Rafael Benevides wrote:
> Before we have a deal with Michelle's team about these content changes, I
> think we should close the two other definitions:
>
> - docs location: move to deltaspike sources, create a new repository, other?
+1 to move to sources
> and
> -docs
On 1 Aug 2014, at 17:46, Rafael Benevides wrote:
> Hi all,
>
> As you may known, Red Hat docs team was called to help on DeltaSpike docs.
> After a long period, they have analyzed the documentation and bring us an
> awesome plan that is available here:
> https://docs.google.com/document/d/18
gt; wrote:
>> Hi all,
>> the website needs an update with details on the 1.0 release.
>> http://deltaspike.apache.org/news.html#8th-release-100-14062014 has a one
>> line statement. :)
>>
>> Congrats to all....
>>
>>
>> On Wed, Jun 18, 201
Hi all,
Now that we have released DeltaSpike 1.0, we have a great opportunity to tell
the world about DeltaSpike.
Arun Gupta (Director of Developer Advocacy at Red Hat) has volunteered to help
us with ways to do this.
Hopefully we can use this thread to start devising a plan.
As a starting p
+1 for blue.
On 14 Jun 2014, at 19:55, Gerhard Petracek wrote:
> hi @ all,
>
> this second vote is about the color and therefore the final logo.
>
> i've uploaded the candidates provided by jim at [1]-[4].
> please send a +1 for one of them.
>
> regards,
> gerhard
>
> [1] http://s.apache.org
I particularly like variant 2 from versions 7 - 10. I like the yellow colour
scheme. I find the purple is too close to the black, and I can’t really see it
- but 9-1, 4 does work.
On 7 Jun 2014, at 22:40, Matt Benson wrote:
> From the peanut gallery, I'd say that applying the gradient from 5-4
I agree, I’m still a fan of #1 here. I like the “retro” look of it :-)
On 3 Jun 2014, at 03:11, James Parenti wrote:
> Hello again,
>
> Here are a couple of updated layouts for the DeltaSpike logo. After a good
> bit of narrowing down, I’ve taken #1 – the preference among most of us – and
> t
I really like #1
On 29 May 2014, at 15:26, James Parenti wrote:
> Hello everyone:
>
> This is a link to another set of revisions. The emblems shown are those that
> have been commented favorably upon. As much as I like the “Geometric” font
> logo, the more I look at it the less I like it or a
Jim’s email bounced.
Here are the logos:
https://www.dropbox.com/sh/6doraoq6ap3qyr3/AABXLSF-LyxEEL29jyHkyWCUa?n=289270217
On 26 May 2014, at 21:03, James Parenti wrote:
> Hello again everyone,
>
> I just revised some of the logos and cleaned up some additional versions I
> was working on an
Hi all,
(Note Rafael is away on vacation atm, so I am responding partly for him ;-)
I definitely agree with getting to 1.0 asap. However also agree that we need to
make sure we are ready.
If there are issues with docs, please open issues, I know Rafael will be
pleased to pick any that are open
Hi all,
I’ve managed to secure some design time from one of Red Hat’s design
contractors, Jim Parenti (based in Chicago, so expect him to respond from that
timezone :-).
I’ve pointed him at http://deltaspike.apache.org and he immediately asked me
"Aside from the description shown on that sampl
in
>>>>
>>>> On Thu, Jan 16, 2014 at 5:41 AM, Gerhard Petracek
>>>> wrote:
>>>>> +1
>>>>>
>>>>> regards,
>>>>> gerhard
>>>>>
>>>>>
>>>>>
>>>&g
Hi all,
Max and Alexey from the JBoss Tools team (http://www.jboss.org/tools/) would
like to see we can improve the DeltaSpike tooling in JBoss Tools. They propose
that we have a Google Hangout with them, and anyone interested from the
DeltaSpike community to kick things off and brainstorm some
h version of ds-jsf-api
> works together with which version of ds-core-impl for example. It gets much
> more complicated with later modules.
>
> Thus I prefer 1.).
>
> LieGrue,
> strub
>
>
>
>
>>
>> From: Pete Muir
+1 to Gerhard’s point (I am looking to try to find someone to help with docs,
but the person I had in mind just left Red Hat :-(. Also +1 to going to 1.0
soon (i.e. making docs and stability a priority!).
On 11 Nov 2013, at 23:09, Gerhard Petracek wrote:
> if we move to v1 soon, we need an use
e id field of the entity
> and convert the entity to its id and vice versa. This could be useful for
> lists or select menus.
>
> Am 19.08.13 16:35 schrieb "Jason Porter" unter :
>
>> Hm, I'll have to go back to the code to see what was done.
>>
>>
The Seam 2 converter worked on any entity class, you just had to provide it
with a reference to the EntityManager.
On 18 Aug 2013, at 05:16, Jason Porter wrote:
> The problem with a generic JSF converter is that it has to be very dumb, or
> you have to use a certain kind of object.
>
>
>
>
I think as we can only do this for annotations in our control, it's less
appealing, as we then end up with both patterns in use.
On 10 Jul 2013, at 12:23, Hugh Nguyen wrote:
> Hi fellow developers,
>
> Instead of creating a whole separate class SomeAnnotationLiteteral and put
> it in some sepa
22 matches
Mail list logo
