Re: [VOTE] Release of Apache DeltaSpike 1.7.0

[Antoine Sabot-Durand]

+1

Le lun. 13 juin 2016 à 13:21, John D. Ament  a
écrit :

> I guess I'll be the first to vote?  Obviously I'm +1 since I ran the
> release twice to make sure no issues...
>
> John
>
>
> On Thu, Jun 9, 2016 at 8:10 PM John D. Ament 
> wrote:
>
> > All,
> >
> > I was running the needed tasks to get the 1.7.0 release of Apache
> > DeltaSpike out.
> > The artifacts are deployed to Nexus [1], the source release available at
> > [2].
> >
> > The tag is available at [3] and will get pushed to the ASF repository
> once
> > the vote passed.
> >
> > The release notes can be found at [4].
> >
> > Please take a look at the 1.7.0 artifacts and vote!
> >
> > Please note:
> > This vote is "majority approval" with a minimum of three binding +1 votes
> > (see [5]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> > and why..
> > 
> >
> > Thanks,
> > John
> >
> > PS - I found a few issues with the release steps, which I will update
> > after the release is complete.
> >
> > [1]
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1038/
> > [2]
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1038/org/apache/deltaspike/deltaspike/1.7.0/
> > [3] https://github.com/johnament/deltaspike/tree/deltaspike-1.7.0
> > [4] https://s.apache.org/DeltaSpike-1.7.0
> > [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
>

Re: Cutting over to Java 7

[Antoine Sabot-Durand]

Beyond Java Level, I think we should start thinking about a CDI 1.2 / Java
EE 7 branch. JDK8 could be nice for this branch but we should make sure
that all Java EE 7 server out there run well on JDK 8

Antoine

Le mar. 12 avr. 2016 à 14:04, Gerhard Petracek 
a écrit :

> @john:
>
> if we have/keep one jdk6 based ci-job and it passes, it's as fine as our
> current support of jdk8 (which is also checked by just one ci-job).
> the rest is up to the ci-servers used for testing the different
> cdi-implementations (and ee-servers).
>
> @"latest version":
> that's why i said "random". it depends on the concrete version available on
> the ci-server/s (we don't control that on our own).
>
> regards,
> gerhard
>
>
>
> 2016-04-12 13:07 GMT+02:00 John D. Ament :
>
> > @gerhard
> > So you're saying its coincidence that the Java 6 versions fail?
> >
> > Basically, its not random releases.  Its the latest Java 6 supported by
> the
> > asf infra on Jenkins.
> >
> > John
> >
> > On Sat, Apr 9, 2016 at 3:42 PM Gerhard Petracek 
> > wrote:
> >
> > > @john:
> > > our ci-jobs are just about the basic compatibility with the different
> > > versions of owb, weld and several (open-source-)ee-servers.
> > > there are only few which test the basic compatibility with different
> > > versions of the jdk explicitly (e.g. jdk8).
> > > we never test against all jdk-releases (it's always a "random" release
> -
> > we
> > > just configure the major-version).
> > > esp. with jdk7 we saw issues caused by different reasons with
> > specific/old
> > > versions of the jdk (in most cases one of the maven-plugins failed ->
> it
> > > wasn't even ds itself).
> > > -> we can never test all >jdk releases< in combination with all
> > > cdi-implementations and ee-servers.
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > 2016-04-09 15:13 GMT+02:00 John D. Ament :
> > >
> > > > Actually the main reason I brought it up was that we currently cannot
> > > > guarantee inter-operability with Java 6 any longer.  If I look at our
> > CI
> > > > tests, very few of the tests that actually run against Java 6
> > > environments
> > > > pass.
> > > >
> > > > This page should give a clearer indication of that problem:
> > > >
> > > >
> > >
> >
> https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20for%20CDI%201.0/
> > > >
> > > > John
> > > >
> > > > On Thu, Apr 7, 2016 at 11:12 AM Cody Lerum 
> > wrote:
> > > >
> > > > > At this point it seems the main driver for dropping Java6 is to
> > > > > discourage its use. I think there is sufficient discouragement
> > > > > elsewhere and anyone with active or new projects is working towards
> > or
> > > > > planning for Java7/8.
> > > > >
> > > > > +1 for keeping Java6 until the next major bump.
> > > > >
> > > > > On Thu, Apr 7, 2016 at 7:25 AM, Mark Struberg
> > >  > > > >
> > > > > wrote:
> > > > > > Agree, we don't gain much with moving to Java7.
> > > > > >
> > > > > > Thus I'd say that we keep Java6/CDI-1.0 and have the next major
> > > version
> > > > > bump (aka DeltaSpike-2.x) targeting Java8 and CDI-2.0. But of
> course
> > > > keep a
> > > > > ds-1.x maintenance branch even after that for a while.
> > > > > >
> > > > > >
> > > > > > LieGrue,
> > > > > > strub
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >> On Thursday, 7 April 2016, 14:42, Gerhard Petracek <
> > > > > gpetra...@apache.org> wrote:
> > > > > >> > as mentioned in the initial discussion i also don't see a real
> > > > > benefit for
> > > > > >> us as a community (to drop the java 6 support at this point).
> > > > > >> in the end ds targets ee6 + supports ee7 servers (including
> > optional
> > > > > >> features).
> > > > > >> ee6 isn't bound to java 6 technically, however, e.g. some
> vendors
> > > > > require
> > > > > >> it...
> > > > > >>
> > > > > >> regards,
> > > > > >> gerhard
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> 2016-04-07 13:18 GMT+02:00 Rooda, William (John.) <
> > wro...@ford.com
> > > >:
> > > > > >>
> > > > > >>>  Ford has an internal “shared farm” of servers that our
> > > applications
> > > > > can
> > > > > >>>  use. The shared farm is Websphere Application Server 8.0.0.x.
> > > This
> > > > > only
> > > > > >>>  has Java6 available.  While some teams go out and spend the
> > money
> > > to
> > > > > >>>  procure their own servers outside of the shared farm, this is
> > > > > prohibitively
> > > > > >>>  expensive without a powerful use case.
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>  Our Java applications won't have a server offering in our
> > internal
> > > > > >> shared
> > > > > >>>  farm for Java 7 until 4Q2016 or 1Q2017 at the earliest. We
> plan
> > on
> > > > > >>>  developing almost all applications against Java6 until that
> > time,
> > > > and
> > > > > >>>  unfortunately we have to re-evaluate continuing to use at an
> > > > > enterprise
> > > > > >>>  level any open source software that no longer patches and
> > supports
> > > > 

Relaunching the idea of a Spring module

[Antoine Sabot-Durand]

Hi all,

Last week at JavaOne I gave 3 talks on CDI and DeltaSpike. I feel a lot of
change since last year: more people, more involved people with advanced
question. I know I didn't met a significant statical sample with the 400 or
500 users I met but my feeling is that Java EE just hit big corporation and
CDI usage in big firms has raised significantly since last year.

A question I had 3 times was about CDI / spring interoperability. The topic
is still the same : We want to adopt CDI and CDI programming model, but we
have a lot of legacy code in Spring, is there any solution to help us
moving to CDI without a Big Bang or keep our existing libs in Spring.
Question was asked by a guy from Wells Fargo, Bank of America and one
insurance I can remember.
If you look at StackOverflow question about Spring CDI interaction you can
see that their frequency is raising as well [1].

That's why I think interesting to relaunch the idea of having a Spring
module in DS. I know there are existing initiatives around so we wouldn't
have to produce it from scratch.

What do you think ?

Antoine


 [1]
http://stackoverflow.com/questions/tagged/cdi+spring?sort=newest&pagesize=50

Re: [VOTE] Release Apache DeltaSpike-1.3.0

[Antoine Sabot-Durand]

+1

Antoine Sabot-Durand

> Le 4 mars 2015 à 10:08, Mark Struberg  a écrit :
> 
> Hi!
> 
> I’d like to call a VOTE for the release of DeltasSpike-1.3.0
> 
> The staging repo is:
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1020/
> 
> The tag is available here:
> https://github.com/struberg/deltaspike/tree/deltaspike-root-1.3.0
> This will get pushed to the ASF repo once the VOTE succeeded.
> 
> The source release is available here:
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1020/org/apache/deltaspike/deltaspike-root/1.3.0/deltaspike-root-1.3.0-source-release.zip
> sha1: 62a9a425c7314811b56f55e3586ff66ce7fe383c
> 
> You can find my key in GIT.
> 
> Guide to testing:
> Add the following to your ~/.m2/settings.xml:
> 
>
>  staging
>  
>
>  apache_staging
>  
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1020/
>  true
>  false
>
>  
>
> 
> Then upgrade your project to 1.3.0 and build with mvn -Pstaging.
> 
> 
> Please VOTE:
> [+1] ship it
> [+0] meh, don’t care
> [-1] stop, there is a problem, ${errorcause}
> 
> The VOTE is open for 72h.
> 
> 
> 
> LieGrue,
> your Apache DeltaSpike Team
> 

Re: [VOTE] Release of Apache DeltaSpike 1.2.1

[Antoine Sabot-Durand]

+1

Antoine Sabot-Durand

> Le 22 déc. 2014 à 20:44, Jason Porter  a écrit :
> 
> +1
> 
>> On Mon, Dec 22, 2014 at 6:50 AM, Mark Struberg  wrote:
>> 
>> +1
>> 
>> LieGrue,
>> strub
>> 
>> 
>> 
>> 
>> 
>>> On Saturday, 20 December 2014, 23:56, Gerhard Petracek <
>> gpetra...@apache.org> wrote:
>>>> Hi,
>>> 
>>> I was running the needed tasks to get the 14th release of Apache
>> DeltaSpike
>>> out.
>>> The artifacts are deployed to Nexus [1] (and [2]).
>>> 
>>> The tag is available at [3] and will get pushed to the ASF repository
>> once
>>> the vote passed.
>>> 
>>> Please take a look at the 1.2.1 artifacts and vote!
>>> 
>>> Please note:
>>> This vote is "majority approval" with a minimum of three +1 votes (see
>>> [4]).
>>> 
>>> 
>>> [ ] +1 for community members who have reviewed the bits
>>> [ ] +0
>>> [ ] -1 for fatal flaws that should cause these bits not to be released,
>> and
>>> why..
>>> 
>>> 
>>> Thanks,
>>> Gerhard
>>> 
>>> [1]
>> https://repository.apache.org/content/repositories/orgapachedeltaspike-1018
>>> [2]
>> https://repository.apache.org/content/repositories/orgapachedeltaspike-1018/org/apache/deltaspike/deltaspike-project/1.2.1/deltaspike-project-1.2.1-source-release.zip
>>> [3]
>> https://github.com/os890/deltaspike-vote/tree/deltaspike-project-1.2.1
>>> [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
> 
> 
> 
> -- 
> Jason Porter
> http://en.gravatar.com/lightguardjp

Re: first steps for the next release

[Antoine Sabot-Durand]

+1 for 1.2.0

> Le 17 nov. 2014 à 19:54, Gerhard Petracek  a 
> écrit :
> 
> hi @ all,
> 
> if there are no objections, i will start with the first steps for the next
> release (v1.2.0) by the end of next week.
> 
> @ v1.2.0 instead of v1.1.1:
> we have some new features (esp. >optional< cdi 1.1+ support - e.g. the
> optional delegation to CDI.current().getBeanManager()).
> 
> regards,
> gerhard

[jira] [Issue Comment Deleted] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotation AnnotatedType

[Antoine Sabot-Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Sabot-Durand updated DELTASPIKE-781:

Comment: was deleted

(was: This patch solves the bug and add a corresponding test)

> AnnotatedTypeImpl doesn't work for Annotation AnnotatedType
> ---
>
> Key: DELTASPIKE-781
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.1.0
>    Reporter: Antoine Sabot-Durand
>Assignee: Antoine Sabot-Durand
> Fix For: 1.1.1
>
>
> I needed to create AnnotatedType for Annotation to register it as an 
> interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
> realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
> contained all the {{Annotation}} class methods where it should have contained 
> none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotation AnnotatedType

[Antoine Sabot-Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Sabot-Durand updated DELTASPIKE-781:

Attachment: (was: DELTASPIKE-781.patch)

> AnnotatedTypeImpl doesn't work for Annotation AnnotatedType
> ---
>
> Key: DELTASPIKE-781
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.1.0
>    Reporter: Antoine Sabot-Durand
>Assignee: Antoine Sabot-Durand
> Fix For: 1.1.1
>
>
> I needed to create AnnotatedType for Annotation to register it as an 
> interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
> realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
> contained all the {{Annotation}} class methods where it should have contained 
> none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Bug corrected in AnnotatedTypeImpl when used to create AnnotatedType for an Annotation

[Antoine Sabot-Durand]

Thanks Gerhard,

It’s done. I close the ticket.

Antoine


> Le 17 nov. 2014 à 10:36, Gerhard Petracek  a 
> écrit :
> 
> hi antoine,
> 
> since you are committer, you are welcome to commit at any time.
> if you would like to discuss something, you can provide a patch or follow a
> discussion-workflow like [1].
> please just ensure that you are using rebase instead of merge (see [2]).
> furthermore, everybody should run mvn clean install (before a push) to
> ensure that our (default-)tests as well as checkstyle are fine.
> 
> regards,
> gerhard
> 
> [1]
> http://deltaspike.apache.org/suggested-git-workflows.html#discussion-workflow-optional
> [2] http://deltaspike.apache.org/suggested-git-workflows.html
> 
> 
> 
> 2014-11-17 10:16 GMT+01:00 Antoine Sabot-Durand :
> 
>> Hi John,
>> 
>> Yes I know I’m listed here, but as I never had the time to contribute to
>> the code (only done communication and help for the new documentation), I
>> thought more respectful to start with a patch. Now as it’s a small
>> correction, I could probably push it myself ;).
>> 
>> Antoine
>> 
>> 
>>> Le 16 nov. 2014 à 19:24, John D. Ament  a écrit
>> :
>>> 
>>> Antoine,
>>> 
>>> I believe you're already a committer on the project, as per [1].
>>> 
>>> John
>>> 
>>> [1]: http://people.apache.org/committers-by-project.html#deltaspike
>>> 
>>> On Sun, Nov 16, 2014 at 1:18 PM, Antoine Sabot-Durand <
>>> anto...@sabot-durand.net> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> While preparing my CDI advanced talk for Devoxx [1] I made an intensive
>>>> use of DeltaSpike core features, especially the AnnotatedTypeBuilder and
>>>> discovered a bug.
>>>> In my talked I wanted to show how to take a third party framework (Drop
>>>> Wizard Metrics) and integrate it with CDI. One step of this integration
>> was
>>>> to declare the @Timed annotation as an interceptor binding using
>>>> BeforeBeanDiscovery#addInterceptorBinding method.
>>>> As @Timed contains two members that I wished to become @NonBinding, I
>>>> decided to use DeltaSpike AnnotatedTypeBuilder to create the required
>>>> AnnotatedType for @Timed. I realised that the builded AnnotatedType
>> didn’t
>>>> contained 2 methods but 6 : the 2 @Timed member + the 4 coming from
>>>> Annotation.
>>>> Yesterday I sent a small patch for this bug in DELTASPIKE-781 including
>>>> test related to this bug.
>>>> 
>>>> Thanks,
>>>> 
>>>> Antoine
>>>> 
>>>> [1] :
>> http://www.slideshare.net/antoinesd/going-further-with-cdi-41411812
>> 
>> 

Re: Bug corrected in AnnotatedTypeImpl when used to create AnnotatedType for an Annotation

[Antoine Sabot-Durand]

Hi John,

Yes I know I’m listed here, but as I never had the time to contribute to the 
code (only done communication and help for the new documentation), I thought 
more respectful to start with a patch. Now as it’s a small correction, I could 
probably push it myself ;).

Antoine


> Le 16 nov. 2014 à 19:24, John D. Ament  a écrit :
> 
> Antoine,
> 
> I believe you're already a committer on the project, as per [1].
> 
> John
> 
> [1]: http://people.apache.org/committers-by-project.html#deltaspike
> 
> On Sun, Nov 16, 2014 at 1:18 PM, Antoine Sabot-Durand <
> anto...@sabot-durand.net> wrote:
> 
>> Hi all,
>> 
>> While preparing my CDI advanced talk for Devoxx [1] I made an intensive
>> use of DeltaSpike core features, especially the AnnotatedTypeBuilder and
>> discovered a bug.
>> In my talked I wanted to show how to take a third party framework (Drop
>> Wizard Metrics) and integrate it with CDI. One step of this integration was
>> to declare the @Timed annotation as an interceptor binding using
>> BeforeBeanDiscovery#addInterceptorBinding method.
>> As @Timed contains two members that I wished to become @NonBinding, I
>> decided to use DeltaSpike AnnotatedTypeBuilder to create the required
>> AnnotatedType for @Timed. I realised that the builded AnnotatedType didn’t
>> contained 2 methods but 6 : the 2 @Timed member + the 4 coming from
>> Annotation.
>> Yesterday I sent a small patch for this bug in DELTASPIKE-781 including
>> test related to this bug.
>> 
>> Thanks,
>> 
>> Antoine
>> 
>> [1] : http://www.slideshare.net/antoinesd/going-further-with-cdi-41411812

Bug corrected in AnnotatedTypeImpl when used to create AnnotatedType for an Annotation

[Antoine Sabot-Durand]

Hi all,

While preparing my CDI advanced talk for Devoxx [1] I made an intensive use of 
DeltaSpike core features, especially the AnnotatedTypeBuilder and discovered a 
bug.
In my talked I wanted to show how to take a third party framework (Drop Wizard 
Metrics) and integrate it with CDI. One step of this integration was to declare 
the @Timed annotation as an interceptor binding using 
BeforeBeanDiscovery#addInterceptorBinding method.
As @Timed contains two members that I wished to become @NonBinding, I decided 
to use DeltaSpike AnnotatedTypeBuilder to create the required AnnotatedType for 
@Timed. I realised that the builded AnnotatedType didn’t contained 2 methods 
but 6 : the 2 @Timed member + the 4 coming from Annotation.
Yesterday I sent a small patch for this bug in DELTASPIKE-781 including test 
related to this bug.

Thanks,

Antoine

[1] : http://www.slideshare.net/antoinesd/going-further-with-cdi-41411812

[jira] [Updated] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotation AnnotatedType

[Antoine Sabot-Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Sabot-Durand updated DELTASPIKE-781:

Summary: AnnotatedTypeImpl doesn't work for Annotation AnnotatedType  (was: 
AnnotatedTypeImpl doesn't work for Annotion AnnotatedType)

> AnnotatedTypeImpl doesn't work for Annotation AnnotatedType
> ---
>
> Key: DELTASPIKE-781
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.1.0
>Reporter: Antoine Sabot-Durand
>Assignee: Antoine Sabot-Durand
> Fix For: 1.1.1
>
> Attachments: DELTASPIKE-781.patch
>
>
> I needed to create AnnotatedType for Annotation to register it as an 
> interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
> realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
> contained all the {{Annotation}} class methods where it should have contained 
> none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotion AnnotatedType

[Antoine Sabot-Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Sabot-Durand resolved DELTASPIKE-781.
-
   Resolution: Fixed
Fix Version/s: 1.1.1

Added a test to avoid adding methods to {{AnnotatedTypeImpl}} if the 
{{AnnotatedType}} is an annotation. Added a small related test as well.

> AnnotatedTypeImpl doesn't work for Annotion AnnotatedType
> -
>
> Key: DELTASPIKE-781
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.1.0
>    Reporter: Antoine Sabot-Durand
>Assignee: Antoine Sabot-Durand
> Fix For: 1.1.1
>
> Attachments: DELTASPIKE-781.patch
>
>
> I needed to create AnnotatedType for Annotation to register it as an 
> interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
> realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
> contained all the {{Annotation}} class methods where it should have contained 
> none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotion AnnotatedType

[Antoine Sabot-Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Sabot-Durand updated DELTASPIKE-781:

Attachment: DELTASPIKE-781.patch

This patch solves the bug and add a corresponding test

> AnnotatedTypeImpl doesn't work for Annotion AnnotatedType
> -
>
> Key: DELTASPIKE-781
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.1.0
>    Reporter: Antoine Sabot-Durand
>Assignee: Antoine Sabot-Durand
> Attachments: DELTASPIKE-781.patch
>
>
> I needed to create AnnotatedType for Annotation to register it as an 
> interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
> realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
> contained all the {{Annotation}} class methods where it should have contained 
> none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotion AnnotatedType

[Antoine Sabot-Durand (JIRA)]

Antoine Sabot-Durand created DELTASPIKE-781:
---

 Summary: AnnotatedTypeImpl doesn't work for Annotion AnnotatedType
 Key: DELTASPIKE-781
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
 Project: DeltaSpike
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.0
Reporter: Antoine Sabot-Durand


I needed to create AnnotatedType for Annotation to register it as an 
interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
contained all the {{Annotation}} class methods where it should have contained 
none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (DELTASPIKE-781) AnnotatedTypeImpl doesn't work for Annotion AnnotatedType

[Antoine Sabot-Durand (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antoine Sabot-Durand reassigned DELTASPIKE-781:
---

Assignee: Antoine Sabot-Durand

> AnnotatedTypeImpl doesn't work for Annotion AnnotatedType
> -
>
> Key: DELTASPIKE-781
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-781
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.1.0
>    Reporter: Antoine Sabot-Durand
>Assignee: Antoine Sabot-Durand
>
> I needed to create AnnotatedType for Annotation to register it as an 
> interceptor binding with {{BeforeBeanDiscovery#addInterceptorBinding}} and 
> realised that the builded {{AnnotatedType}} thru {{AnnotatedTypeBuilder}} 
> contained all the {{Annotation}} class methods where it should have contained 
> none. That makes the container (Weld or OWB) crash.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: DeltaSpike docs plan

[Antoine Sabot-Durand]

+1 for me as well. Having the doc source with source code is a must have
IMO.

Antoine Sabot-Durand

Le 4 août 2014 à 17:52, Jason Porter  a écrit :

Wow, looks like a lot of work was spent on the analysis of the
documentation! Thanks Michelle!

+1 from me for all the suggestions.


On Fri, Aug 1, 2014 at 10:46 AM, 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/186f_amQ9XuREq8FcO7orxvOjQZtvEEYa7WPj1e8p8bM/edit#heading=h.4sqhyz68wgg2
>
> The document is opened for comments.
>
> Something that was also discussed not only inside Red Hat but with some
> community members is about the format and source of the documentation. I
> strongly believe that we should have the documentation somewhere else but
> the DS site source. It could improve the ease to the community to
> contribute with it. Having said that, it's also suggested that we should
> use asciidoc as documentation format.
>
> So what we have until now ?
>
> - The documentation plan to be reviewed and approved by the DS community.
> Then we can talk about the plans to make it happen.
> - The documentation location: Recommendation to be out of the site source.
> - The documentation format: Suggested to use asciidoc.
>
> Please, read the plan and lets discuss about these 3 topics individually.
>
> Michelle Murray (whose team provided the plan and she is copied on this
> Thread) can follow the feedback.
> --
>
> *Rafael Benevides | Senior Software Engineer*
> JBoss Developer
> M: +55-61-9269-6576
>
> [image: Red Hat]
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com
>
> [image: LinkedIn] <http://www.linkedin.com/company/3258288> [image:
> Youtube] <https://www.youtube.com/redhatlatam>
>



-- 
Jason Porter
http://en.gravatar.com/lightguardjp

Re: Documentation proposal

[Antoine Sabot-Durand]

Thanks Romain for your answer
Le 23 juin 2014 à 15:41, Romain Manni-Bucau  a écrit :

> Hi Antoine
> 
> 2014-06-23 20:52 GMT+02:00 Antoine Sabot-Durand :
> 
>> Hi all,
>> 
>> 
>> This week-end I wanted to check out documentation source to see how to
>> contribute to it.
>> I took me a lot of time to find where the doc source are. I finally found
>> it in the mailing list thanks to Rafael ;).
>> 
>> That brought me to a more general reflexion around Deltaspike
>> documentation. Here are my 2 cents :
>> 
>> 1) Shouldn’t we at least put a link to the site svn to give opportunity to
>> more people to contribute to the doc ?
>> 
> 
> +1, on tomee site we added a little button to edit the page (for instance
> http://tomee.apache.org/examples/ right of the twitter button)
> 
> 
>> 2) Shouldn’t we move the doc to the project to have it at he same place
>> than the code ?
>> 
> 
> +1000 even if almost no apache project does it, personally I almost only
> update docs if in the same project
> 
> 
>> 3) Shouldn’t we use a doc generator that could also produce PDF to have an
>> offline manual (a lot of my former coworkers use to read documentation
>> while commuting). Asciidoctor is my better known tool (I’m using it to
>> manage and generate CDI specification doc) and markdown can be easily
>> translate to asciidoc, but it can be something else.
>> 
>> 
> +1 but needs time since it will need to be integrated with apache cms IMHO
> (ie a generic solution all apache projects will reuse). adoc is nice and
> usable but maybe we should ping infra to officially support it otherwise I
> think markdown is a better choice (maybe using pandoc to go to pdf)
> 

True except if we consider the doc as a deliverable like binaries. If it’s part 
of the project we could imagine delivery an HTML page and a PDF file and put a 
link in the site. The idea would be to remove the doc from the CMS and have the 
CMS points to it. I don’t know if it fits with Apache policy but considering 
the documentation problem we have, we really should do something to encourage 
contribution.


> 
>> As a first significant contribution to the project I propose doing 2 and 3.
>> 
>> WDYT?
>> 
>> 
>> Antoine Sabot-Durand
>> ———
>> Twitter : @antoine_sd
>> CDI co-spec lead & eco-system development
>> Agorava tech lead
>> 
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Documentation proposal

[Antoine Sabot-Durand]

Hi all,


This week-end I wanted to check out documentation source to see how to 
contribute to it.
I took me a lot of time to find where the doc source are. I finally found it in 
the mailing list thanks to Rafael ;).

That brought me to a more general reflexion around Deltaspike documentation. 
Here are my 2 cents :

1) Shouldn’t we at least put a link to the site svn to give opportunity to more 
people to contribute to the doc ?
2) Shouldn’t we move the doc to the project to have it at he same place than 
the code ?
3) Shouldn’t we use a doc generator that could also produce PDF to have an 
offline manual (a lot of my former coworkers use to read documentation while 
commuting). Asciidoctor is my better known tool (I’m using it to manage and 
generate CDI specification doc) and markdown can be easily translate to 
asciidoc, but it can be something else.

As a first significant contribution to the project I propose doing 2 and 3.

WDYT?


Antoine Sabot-Durand
———
Twitter : @antoine_sd
CDI co-spec lead & eco-system development
Agorava tech lead



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Promoting and evangelising DeltaSpike

[Antoine Sabot-Durand]

I plan writing blog post about Deltaspike mainly about undocumented features 
like BeanBuilder but also about config.
Perhaps we should coordinate actions around Deltaspike promotion (blog, talk) 
to avoid speaking of the same thing?

Antoine




Le 21 juin 2014 à 00:37, Arun Gupta  a écrit :

> I saw the announcement but it barely provide any detail for a 1.0 
> announcement :)
> 
> I like to provide context, background, download and other relevant details in 
> my blog. Guess will scavenge that information myself.
> 
> Arun
> 
> On 6/20/14, 3:28 PM, Gerhard Petracek wrote:
>> hi arun,
>> 
>> as a first and easy step everybody is very welcome to retweet our 
>> announcements - esp. about v1 (see [1]).
>> 
>> regards,
>> gerhard
>> 
>> [1] https://twitter.com/DeltaSpikeTeam/status/479174218131972096
>> 
>> 
>> 
>> 2014-06-21 0:13 GMT+02:00 Arun Gupta > >:
>> 
>>Any suggestions on this ?
>> 
>>Arun
>> 
>> 
>>On 6/18/14, 9:08 AM, Pete Muir wrote:
>> 
>>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 point, I know Arun was looking for an overview
>>of 1.0, so he can see what to blog and tweet about. I had a
>>quick look around, but I couldn’t find anything like this.
>> 
>>Pete
>> 
>> 
>>-- http://blog.arungupta.me
>>http://twitter.com/arungupta
>> 
>> 
> 
> -- 
> http://blog.arungupta.me
> http://twitter.com/arungupta



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] logo-shape

[Antoine Sabot-Durand]

+1 for #1
+1 for #5

Antoine

Le 11 juin 2014 à 18:51, Gerhard Petracek  a écrit :

> hi @ all,
> 
> this first vote is just about the basic shape/style and >not< the color.
> 
> i've uploaded the candidates provided by jim at [1].
> please send a +1 for one (or two) logo shape/s.
> (there will be a 2nd vote about the color afterwards.)
> 
> regards,
> gerhard
> 
> [1] http://s.apache.org/DS_LOGO1_VOTE1



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Replace @Web with a common DeltaSpike qualifier

[Antoine Sabot-Durand]

+1 for @Deltaspike qualifier : it gives a solution to manage co-existence of DS 
feature and future CDI standardized DS features.


Le 24 févr. 2014 à 10:16, Romain Manni-Bucau  a écrit :

> +1 as well for a global qualifier @DeltaSPike
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
> 
> 
> 
> 2014-02-24 9:52 GMT+01:00 Thomas Andraschko :
>> +1 for @DeltaSpike -> @Inject @DeltaSpike ServletContext
>> 
>> 
>> 2014-02-24 9:52 GMT+01:00 Thomas Andraschko :
>> 
>>> Hi,
>>> 
>>> based on the discusstion in "Servlet Module - Do we really need @Web?",
>>> I'd like to call a vote.
>>> 
>>> The idea is to replace @Web with a common qualifier because @Web is
>>> redudant:
>>> @Inject @Web ServletContext.
>>> 
>>> We could also reuse this qualifier for other features in the future.
>>> 
>>> 1) Should we replace it?
>>> 2) What about the name? @DeltaSpike?
>>> 
>>> Regards,
>>> Thomas
>>> 

Re: [DISCUSS] next release version? 0.6 or 1.0?

[Antoine Sabot-Durand]

Yes Ove, too few Red Hat committers. But they’re will be one more when CDI 1.2 
will be out and work for preparing CDI 2.0 will be on track.

Antoine Sabot-Durand
———
Twitter : @antoine_sd
CDI co-spec lead & eco-system development
Agorava tech lead


Le 16 févr. 2014 à 22:38, Ove Ranheim  a écrit :

> The commit graph shows too few committers.. and I appreciate your work! 
> 
> I also notice too few Redhat/JBoss Weld/Seam committers left on the project. 
> How come?
> 
> /ove
> 
> On 16. feb. 2014, at 22:10, Gerhard Petracek  
> wrote:
> 
>> hi ove,
>> 
>> i was only talking about the commits.
>> 
>> regards,
>> gerhard
>> 
>> http://www.irian.at
>> 
>> Your JSF/JavaEE powerhouse -
>> JavaEE Consulting, Development and
>> Courses in English and German
>> 
>> Professional Support for Apache MyFaces
>> 
>> 
>> 
>> 2014-02-16 22:07 GMT+01:00 Thomas Andraschko :
>> 
>>> +1 Ove
>>> We are really late for an 0.6. I would release 0.6 this/next month and
>>> after that, lets finish 1.0.
>>> We should fix all open issues and finish the documentation!
>>> 
>