Ok since someone pointed me privately towards it, a vote seems to become
invalid if there are changes between the vote and the release.
Then let me pull the vote off the list for now and then I will do the
changes regarding the master pom and the code cleanup and will restart
the vote again next week.
Any objections?
Werner
Werner Punz schrieb:
Ok I noted it down in the jira, thanks also for adding the comment, I am
currently in huge code cleanup tasks before the alpha, this will go in.
Werner
Matthias Wessendorf schrieb:
ah! ok,
I'd recommend to use the newly released Apache-MyFaces-Master7
On Tue, Feb 2, 2010 at 10:51 AM, Mark Struberg <strub...@yahoo.de> wrote:
any <parent> section is still missing ;)
LieGrue,
strub
--- On Tue, 2/2/10, Matthias Wessendorf <mat...@apache.org> wrote:
From: Matthias Wessendorf <mat...@apache.org>
Subject: Re: [VOTE] Extensions-Scripting Alpha
To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Tuesday, February 2, 2010, 10:36 AM
...which inherits from Apache-7
On Tue, Feb 2, 2010 at 10:35 AM, Matthias Wessendorf
<mat...@apache.org>
wrote:
MyFaces has its own master-pom
-Matthias
On Tue, Feb 2, 2010 at 10:32 AM, Mark Struberg <strub...@yahoo.de>
wrote:
Hi Werner!
Not sure if this is needed in your case, but the
pom in extensions/scripting/trunk doesn't contain a
<parent> section.
Usually this points (in the end) to
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>6</version>
</parent>
for all Apache projects.
LieGrue,
strub
--- On Tue, 2/2/10, Werner Punz <werner.p...@gmail.com>
wrote:
From: Werner Punz <werner.p...@gmail.com>
Subject: [VOTE] Extensions-Scripting Alpha
To: dev@myfaces.apache.org
Date: Tuesday, February 2, 2010, 9:26 AM
Hello everyone, I have been feature
complete since last week for the alpha
release. So I want to
start the vote for the Ext-Scripting Alpha 1.
Feature summary:
The planned Spring part will not make it into
the official
1.0 release
since works on dependency injection frameworks
which can
provide beans over the EL will become integral
part post 1.0
(my plan is to also go the CDI route if the
frameworks
permit it),the spring reloading it will be
merged over time,
but will not be part of the official 1.0.
So for now 1.0 will only support JSF and JSF
only, but that
extensively.
Since I am feature complete and relatively
bugfree all the
work from now on will go into bugfixing and
code cleanup
(believe me some parts really need that)
Here is a short compressed summary of what
will go into the
alpha 1.0 and later final version:
Dynamic loading of all JSF 1.2 artifacts,
including
Application and Session scoped beans (lots of
work went into
this area to enable that)
Dynamic loading of most JSF 2.0 artifacts
(application
events currently are not supported)
Dynamic JSF2 annotation support (aka push
annoations into
existing classes move them around as you
wish)
Dynamic resource loading within JSF2 (aka load
resources
from your source path)
Dynamic XHTML loading for Facelets (load your
xhtml
templates directly from your sourcepath)
And all of this for Groovy and Java
The documentation will be hosted on the Wiki
for the time
being and is a work in progress, but enough
material already
is there to justify an alpha release as well:
http://wiki.apache.org/myfaces/Extensions/Scripting
As I said, feature freeze for now, and all
which will go
into the alphas and betas will be code cleanup
and bugfixes
to get a 1.0 release out sometime around
March.
Werner
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
