I agree with Rainer, commit rights to xwork have been granted to S2
committers on-demand (like me), where the project is, I don't think matters
much. I am set on getting periodic S2 builds out, and then I will try to do
the same with XWork, first I need to get Rainer and Rene to document the
proces
Great news, thanks for your interest!
Your patches and feedback have been very helpful in the past,
I'm looking forward to get more :)
You'll receive a private message soon...
cheers,
Rainer
> On Sun, 2008-11-16 at 00:31 +0100, Rainer Hermanns wrote:
> [snip]
>> I wouldn't have a problem to move
On Sun, 2008-11-16 at 00:31 +0100, Rainer Hermanns wrote:
[snip]
> I wouldn't have a problem to move over XWork to the ASF and I am pretty
> sure some other XWork developers would vote +1 for this step, but just
> bringing over a project to the ASF without new volunteer developers
> wouldn't solve
Musachy,
I'll have a look in the next couple of days.
I'll contact you on IRC during the week.
cheers,
Rainer
> On our super long convention thread, we got to the agreement that in order
> to move convention out of the sandbox, there should be a way to run both
> plugins side by side, so backwar
It is not true, that there are no releases of XWork.
True is, that the releases are not that frequent as required.
Currently only Musachy and me are working on XWork and applying patches.
Both of us are Struts2 core developers and PMC members, so you can be sure
that there will be XWork releases as
Fix away as you find things that are not right.
musachy
On Sat, Nov 15, 2008 at 3:19 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 15, 2008 at 1:14 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > On Fri, Nov 14, 2008 at 12:29 PM, Musachy Barroso <[EMAIL PROTECTED]>
> wrote:
> >
> >>
> h
On Sat, Nov 15, 2008 at 1:14 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 14, 2008 at 12:29 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
>
>> https://svn.apache.org/repos/asf/struts/struts2/branches/release_process
>
> The first thing I notice is that the gpg signing is in the default
--- On Sat, 11/15/08, Struts Two <[EMAIL PROTECTED]> wrote:
> It makes u wonder what happens if XWORK for some reason or
> other goes out of commission and there are no releases.
Besides the fact that there are a few S2 committers who are also XWork
committers I think you've misunderstood how op
On Fri, Nov 14, 2008 at 12:29 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> https://svn.apache.org/repos/asf/struts/struts2/branches/release_process
The first thing I notice is that the gpg signing is in the default
build. If you put it in a profile with an id of 'release' then it
will be act
On Sat, Nov 15, 2008 at 12:01 PM, Struts Two <[EMAIL PROTECTED]> wrote:
> I count not help myself not to ask the queston and still wonder why it was
> decided to build struts 2 on XWork instead of directing the effort to come
> up with struts 2 using something home grown technologies like Command
I count not help myself not to ask the queston and still wonder why it was
decided to build struts 2 on XWork instead of directing the effort to come up
with struts 2 using something home grown technologies like Command chains (
that is currently used in struts 1.3 +). It makes u wonder what hap
On our super long convention thread, we got to the agreement that in order
to move convention out of the sandbox, there should be a way to run both
plugins side by side, so backward compatibility could be possible. The
remaining issue to make that happen was to implement "multiple unknown
h
This great news guy, both the XWork 2.0.7 release and the improvements
on the release process. I'll start now with the Struts 2.0.14 build
process, along with trying to backport the release process improvements.
Let's roll :)
Musachy Barroso schrieb:
We are trying to get the release process
We are trying to get the release process in a better shape, so
documenting/improving the xwork release process would be great. Is there any
documentation for xwork releases? Feel free to add stuff here:
http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution-new.html
I wi
Hi,
xwork 2.0.7 is released and you can kick off the S2.0.14 release process.
I'd love to get more S2 developers into the XWork development process.
So, are there any S2 (or other interested) developers not yet involved in
XWork who'd like commit access? Please contact me by mail and I'll add
you
I totally agree that this is currently a very bad situation. Jeromy's
tip for static resources is a working fix for the 2.0.12 issue, as well
as an uprgade to 2.0.13 testing version would be (this was no GA
release). Please note that we fixed the static resource bug immediately
when it was repo
16 matches
Mail list logo
