Ok, Mark :) You would also create the jira tickets for features under the release version (M1or M2 ..M5) you think that will provide these functionalities.
Thanks; /Gurkan ________________________________ From: Mark Struberg <[email protected]> To: [email protected] Sent: Saturday, January 24, 2009 9:05:45 AM Subject: Re: AW: how to cope with 'additional' features of OpenWebBeans over the Spec Gurkan, you are absolutely right that there is currently no need to force such features. But on the other hand, there will be the point when we will like to add one or the others of them. And since I'm a little forgetfully, I better write things down immediately ;) LieGrue, strub --- Gurkan Erdogdu <[email protected]> schrieb am Sa, 24.1.2009: > Von: Gurkan Erdogdu <[email protected]> > Betreff: Re: AW: how to cope with 'additional' features of OpenWebBeans over > the Spec > An: [email protected] > Datum: Samstag, 24. Januar 2009, 17:48 > For me ,content is looking good Mark. But do we have to > put such a content before the implementation contains those > futures ? > > I think that firstly we have to order our priorities for > the jira tasks that are waiting to be solved. Currently, > there are two milstone versions, namely M1 and M2 in the > jira. I will add other milstone versions, M3, M4, M5 and > finally the 1.0.0 version. After that we may partitioned the > our issues over these versions. Before each milestone is > released, we can work on the issues it has. > > What do you think guys about the above process? > > * 5 milestone versions are enough before the 1.0.0 version? > * If you think that we follow another path for our > releasing process, please give us an information about it. > > Thanks; > > /Gurkan > > > > > ________________________________ > From: Mark Struberg <[email protected]> > To: [email protected] > Sent: Saturday, January 24, 2009 7:47:09 AM > Subject: AW: how to cope with 'additional' features > of OpenWebBeans over the Spec > > I'd like to add a site (+functionality behind) with the > following content: > > -------------- > Extensions over the JSR-299 Specification > > This section contains a list of functionality in > OpenWebBeans > which is not covered by the official specification. > > OpenWebBeans is fully compatible with the JSR-299 > standard if > the default configuration is being used. Nevertheless > some parts > of the behaviour may be changed and some functionality > is > additionally available. > > Please note that using the mentioned functionality can > cause > that your application may not be run on other WebBeans > implementations. > > OpenWebBeans may be configured that a WARNING message > will be logged > whenever any of this additional functionality is being > used. > -------------- > > The configuration may be done with openwebbeans.properties > as explained below. > > > LieGrue, > strub > > > --- Mark Struberg <[email protected]> schrieb am Sa, > 24.1.2009: > > > Von: Mark Struberg <[email protected]> > > Betreff: how to cope with 'additional' > features of OpenWebBeans over the Spec > > An: [email protected] > > Datum: Samstag, 24. Januar 2009, 14:56 > > Hi! > > > > I'd like to know how we should cope with features > we > > implement in OpenWebBeans which are _not_ specified in > > JSR-299 but are quite handy to have. > > > > 1.) Do we like to have such 'additional > features' > > at all? > > I'd say yes, e.g. the injection of java primitives > and > > wrappers for constructors and producers would be very > > valuable in praxis. Also a few optional configurations > like > > to use a different name for 'beans.xml' > > > > 2.) If so, how do we document it? > > My preference would be to add a page for each > extension in > > src/site/apt/extensions > > > > LieGrue, > > strub
