A little late from the vacancies ...
Martin Cooper schrieb:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http://incubator.apache.org/ip-clearance/index.html
of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http://incubator.apache.org/ip-clearance/index.html
The XWork artifacts and software grant are available for your perusal here:
https://issues.apache.org/struts/browse/WW-3248
Upon
,
Wes, Lukasz and Rene, all of whom are Struts committers already.
That's largely the point.
--
Martin Cooper
Niall
On Sat, Dec 26, 2009 at 7:11 PM, Martin Cooper mart...@apache.org wrote:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony
:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http://incubator.apache.org/ip-clearance/index.html
The XWork artifacts and software grant are available for your
-Original Message-
From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Saturday, December 26, 2009 14:50
To: Struts Developers List
Subject: Re: [VOTE] Accept the XWork project as donated by
OpenSymphony
[X] Yes, accept
-Original Message-
From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Saturday, December 26, 2009 14:50
To: Struts Developers List
Subject: Re: [VOTE] Accept the XWork project as donated by
OpenSymphony
[X] Yes, accept
-Original Message-
From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Saturday, December 26, 2009 14:50
To: Struts Developers List
Subject: Re: [VOTE] Accept the XWork project as donated by
OpenSymphony
[X] Yes, accept
[X ] Yes, accept the XWork project
On Mon, Dec 28, 2009 at 12:54 AM, Jason Pyeron jpye...@pdinc.us wrote:
-Original Message-
From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Saturday, December 26, 2009 14:50
To: Struts
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http://incubator.apache.org/ip-clearance/index.html
The XWork artifacts and software grant are available for your
My own vote:
On Sat, Dec 26, 2009 at 11:11 AM, Martin Cooper mart...@apache.org wrote:
[X] Yes, accept the XWork project
[ ] I don't really care one way or the other
[ ] No, do not accept the XWork project, for these reasons (please specify)
--
Martin Cooper
On Sat, Dec 26, 2009 at 12:11 PM, Martin Cooper mart...@apache.org wrote:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http://incubator.apache.org/ip-clearance
[X] Yes, accept the XWork project
On Sat, Dec 26, 2009 at 11:11 AM, Martin Cooper mart...@apache.org wrote:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http
[X] Yes, accept the XWork project
On Sat, Dec 26, 2009 at 11:11 AM, Martin Cooper mart...@apache.org wrote:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project from OpenSymphony. This is a required step of the IP
Clearance procedure documented here:
http
[x] Yes, accept the XWork project
-Wes
On 12/26/09, Musachy Barroso musa...@gmail.com wrote:
[X] Yes, accept the XWork project
On Sat, Dec 26, 2009 at 11:11 AM, Martin Cooper mart...@apache.org wrote:
This is a vote for the Struts PMC to formally accept the donation of
the XWork project
Don Brown wrote:
On Jan 3, 2008 5:44 AM, Brian Pontarelli [EMAIL PROTECTED] wrote:
What is the policy for Struts committers getting access to XWork? While
updating the convention plugin I had to change a few things in XWork and I
want to make sure that they get committed to trunk before I
The backstory is that we proposed bringing over WebWork as Struts 2,
we decided to leave XWork at OpenSymphony. One reason is that most of
us like the strong separation between XWork and Struts 2, so as to
keep HTTP from creeping back in the core API. Another reason is that
incubating a large
If the codebases are to remain separate, I'd like to suggest that all
Struts2 committers are added to XWork. The reason that I say that is the
codebases are so coupled. If you look through comments in XWork, you
start to see more references directly to Struts2. Struts2 won't function
unless
Not every Struts committer works on Struts 2, and not every committer
working on Struts 2 wants to work on XWork too. It's a security
exception to give people accounts that they haven't requested and may
never use.
AFAIK, to date, anyone here who wanted access to XWork has gotten it
without any
What is the policy for Struts committers getting access to XWork? While
updating the convention plugin I had to change a few things in XWork and I
want to make sure that they get committed to trunk before I start using the
convention plugin on projects. I have a few bugs open, but it could take a
I have asked about this before but I never got an answer. Just assign
a couple of patches to Rainer and bother him on #struts and he will
give you commit rights. (that's what I unintentionally did :) )
musachy
On Jan 2, 2008 1:44 PM, Brian Pontarelli [EMAIL PROTECTED] wrote:
What is the policy
On Jan 3, 2008 5:44 AM, Brian Pontarelli [EMAIL PROTECTED] wrote:
What is the policy for Struts committers getting access to XWork? While
updating the convention plugin I had to change a few things in XWork and I
want to make sure that they get committed to trunk before I start using the
On Jan 2, 2008 2:26 PM, Don Brown [EMAIL PROTECTED] wrote:
At this point, our plan is to leave them where they are. I'd like to
get rid of OGNL through the JUEL plugin, and perhaps just include the
xwork code inside the Struts jar, dropping our dependency list down to
just Freemarker.
If we
In a perfect world, we would have the theme system in core, then a
Freemarker theme plugin that implements it for Freemarker (same for
velocity). Still there are a couple other areas we use freemarker,
the debug screen comes to mind. That probably doesn't need something
as powerful as
23 matches
Mail list logo