ys think?
rgds
- Original Message
From: Ted Husted <[EMAIL PROTECTED]>
To: Struts Developers List
Sent: Friday, 6 October, 2006 4:26:53 PM
Subject: Re: Struts 2.0.1 release
Has anyone volunteered to work on the XWork docs?
The XW2 docs aren't any better or worse than the XW 1.
er, 2006 4:26:53 PM
Subject: Re: Struts 2.0.1 release
Has anyone volunteered to work on the XWork docs?
The XW2 docs aren't any better or worse than the XW 1.1 docs, and I
believe that release series was getting the "ready for prime time"
stamp.
Is anyone besides Struts 2.0.x trying to
From a user's standpoint, I agree, the core is solid and ready for GA.
I'm finding feature enhancements that I'd like to see, but not
necessarily bugs/issues.
Hope that helps. . .
David
Don Brown wrote:
Yeah, sorry, that is what I was trying to say - I'm fine with freezing
the API here, pus
Yep, that does it!
-Ted.
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Try this: mvn clean install site -P
xwork,plugins,apps,all,itest,pre-assembly
You don't need core, and I put the toolbox module in the default profile
(there was no toolbox profile).
Don
Ted Husted wrote:
> On 10/6/06,
Yeah, sorry, that is what I was trying to say - I'm fine with freezing
the API here, pushing future improvements into 2.1 or 3.0. I think we
are 100% on the same page here :)
Let's get this puppy rolled!
Don
Ted Husted wrote:
Well, we wouldn't want to *break* the API in the same release ser
Well, we wouldn't want to *break* the API in the same release series,
since that's what a release series is suppose to mean. If we want to
break the API, we should go onto the next series (2.1 or 3.0). Though,
if we were to break the API, we'd also break WW2 compatibility, and
that's suppose to be
Hmm...could Struts 2.0.1 go GA...I hadn't really thought about it
before. For me, the main thing that GA does is mean that you can't
screw with the API anymore in that branch. Therefore, if we needed to
do anything significant, we'd have to do it in a new branch, and put the
old API through t
Try this: mvn clean install site -P
xwork,plugins,apps,all,itest,pre-assembly
You don't need core, and I put the toolbox module in the default profile
(there was no toolbox profile).
Don
Ted Husted wrote:
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymo
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymore. The code has been split into
different "plugins". A plugin is a specific extension to the Struts
framework that, by definition, isn't "core". This allows us to more
easily manage a codebase that integrat
Has anyone volunteered to work on the XWork docs?
The XW2 docs aren't any better or worse than the XW 1.1 docs, and I
believe that release series was getting the "ready for prime time"
stamp.
Is anyone besides Struts 2.0.x trying to use XWork in production? Is
there even an XWork forum any more?
Works for me.
Don
Ted Husted wrote:
Right now, I count 12 Struts 2 JARs, plus struts2-all, 9 of which are
plugins. For a quality vote, I'd expect we could just list them all
and let people break out JARs in a different grade s. For example,
+1 GA
struts2-core
struts2-toolbox
struts2-config-br
Right now, I count 12 Struts 2 JARs, plus struts2-all, 9 of which are
plugins. For a quality vote, I'd expect we could just list them all
and let people break out JARs in a different grade s. For example,
+1 GA
struts2-core
struts2-toolbox
struts2-config-browser-plugin
struts2-sitemesh-plugin
st
Sounds good to me. The person calling the vote could put forth the list
of plugins that fall under each grade? There are certainly some I trust
more than others :)
Don
Ted Husted wrote:
OK, how about the same release cycle but independant grades. The
notion being that we could vote Struts C
OK, how about the same release cycle but independant grades. The
notion being that we could vote Struts Core GA, but leave the Tiles
Plugin at Alpha or Beta.
-Ted.
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
We could spin plugins off into their own project, with their own release
cycle, bu
We could spin plugins off into their own project, with their own release
cycle, but I'm afraid we don't have the development support to maintain
and release all those plugins. By keeping them in the Struts 2 release
cycle, we ensure they are maintained and supported. Ideally, yes, they
would
Agreed.
Don
Ted Husted wrote:
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymore. The code has been split into
different "plugins". A plugin is a specific extension to the Struts
framework that, by definition, isn't "core". This allows us to more
easil
Sounds good. I'll be online on MSN, AIM, GTalk, etc. Also, you can
call my cell.
Don
Ted Husted wrote:
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Saturday afternoon is fine with me, however, I'll be at ApacheCon
already, but I'm sure there will be internet access somewhere. My only
c
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Saturday afternoon is fine with me, however, I'll be at ApacheCon
already, but I'm sure there will be internet access somewhere. My only
concern, as Wendy said, is to have XWork rolled first.
Tell you what. Check out the Internet access, and if
On 10/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
To clarify, there is no "extras" anymore. The code has been split into
different "plugins". A plugin is a specific extension to the Struts
framework that, by definition, isn't "core". This allows us to more
easily manage a codebase that integrat
Would a plugin even need to be part of the core or extra JAR?
Other products based on plugins tend to distribute each plugin separately.
Sometimes plugins come bundled with a greater release, but, in most
cases, I believe any of the bundled plugins could be released
separately if a fix were need
Ted Husted wrote:
This policy of grading a release at the lowest common denominator
doesn't seem to be working out all that well. Different parts of the
distribution have different levels of 'quality' so to speak. If you
have an experimental plugin, that's no reason to downgrade the core.
Th
On 10/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> The reason I ask is that our 2.0.1 release will be tied to whatever
> version moniker that XWork uses. If tomorrow's XWork release is tagged
> as "beta", and that cannot change for that set of
I absolutely agree! That is one of the advantages of the plugin
system. What would be the best way to inform users of the
"experimental" quality of a plugin? The Linux kernel uses the
"experimental" label to inform the user that a particular module isn't
deemed "production quality". Can we
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
The reason I ask is that our 2.0.1 release will be tied to whatever
version moniker that XWork uses. If tomorrow's XWork release is tagged
as "beta", and that cannot change for that set of bits, then the 2.0.1
release will also be forever beta.
rote:
I want to roll the Struts 2.0.1 release next weekend, October 8. A lot
of changes have gone into the code since 2.0.0 and I'd like to have a
solid release that people can check out after Ted and my talks.
I'm thinking we'll do this at the Sunday hackathon since I believe T
XWork does use the alpha, beta, stable tagging of releases, however, the
release process is lightweight and many people have commit access. I
do, and you just need to ask Patrick to get access yourself. To be
honest, this XWork release shouldn't go 2.0.0 final, because the
documentation for X
Yes.
Though, does XWork the release process allow for updating the bits
from beta to stable or GA?
The reason I ask is that our 2.0.1 release will be tied to whatever
version moniker that XWork uses. If tomorrow's XWork release is tagged
as "beta", and that cannot change for that set of bits, th
Ted,
I am planning a beta-1 release of xwork 2.0 for tomorrow.
This will be tagged and build with a fixed version number.
Would this fit into your timeframe?
Rainer
> I don't have karma to XWork, so it's not something I could tag myself.
>
> -Ted.
>
> On 10/6/06, Wendy Smoak <[EMAIL PROTECTED]>
I don't have karma to XWork, so it's not something I could tag myself.
-Ted.
On 10/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> I'm wondering if maybe we should roll this tomorrow afternoon instead.
> They might be working on the Internet con
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I'm wondering if maybe we should roll this tomorrow afternoon instead.
They might be working on the Internet connection on Monday, and my
tutorial is Monday afternoon. It would be nice to have it before I
leave, so that I can put it on the tutori
ridge classes.
-Ted.
On 9/29/06, Don Brown <[EMAIL PROTECTED]> wrote:
I want to roll the Struts 2.0.1 release next weekend, October 8. A lot
of changes have gone into the code since 2.0.0 and I'd like to have a
solid release that people can check out after Ted and my talks.
I'm t
Looks good to me, nice job!
Don
Ted Husted wrote:
The PRC is asking for the usual press releases for ApacheCon. I
thought we might want to forward something about Struts 2.0.1.
I appended a proposed draft to the release plan.
*
http://cwiki.apache.org/WW/release-plan-201.html#ReleasePlan2.0.
The PRC is asking for the usual press releases for ApacheCon. I
thought we might want to forward something about Struts 2.0.1.
I appended a proposed draft to the release plan.
*
http://cwiki.apache.org/WW/release-plan-201.html#ReleasePlan2.0.1-DraftAnnouncementforApacheCon
-Ted.
-
ame, name, etc.
I'd like to see how the Able project will handle
this one, as they are
looking to work over Struts using a comprehensive
convention-based
approach.
Don
David H. DeWolf wrote:
Sounds good to me too. . .
any hope of convincing one of you to apply this
(or a similar)
Sounds good, I'll send you my cell number. Wendy, will you be online on
Sunday at all?
Don
Ted Husted wrote:
On 9/29/06, Don Brown <[EMAIL PROTECTED]> wrote:
Really? Dang it, I'm flying in on Saturday night, as I thought it was
Saturday and Sunday :/ Well, ok, I guess we'll roll 2.0.1 Monda
From https://issues.apache.org/struts/browse/WW-1458
<@s.textfield name="user.userName"
value="%{user.userName}"
label="%{getText('user.userName')}"/>
As discussed on the mailing list, the value is already defaulted to
the name, so the (very common) idiom in question is
<@s.textfield name=
ased
> approach.
>
> Don
>
> David H. DeWolf wrote:
> > Sounds good to me too. . .
> >>
> >> any hope of convincing one of you to apply this
> (or a similar) patch
> >> prior to the release:
> >>
> >> https://issues.apac
pproach.
Don
David H. DeWolf wrote:
Sounds good to me too. . .
any hope of convincing one of you to apply this (or a similar) patch
prior to the release:
https://issues.apache.org/struts/browse/WW-1458
Thanks,
David
Don Brown wrote:
I want to roll the Struts 2.0.1 release next weekend, Octob
te:
I want to roll the Struts 2.0.1 release next weekend, October 8. A
lot of changes have gone into the code since 2.0.0 and I'd like to
have a solid release that people can check out after Ted and my talks.
I'm thinking we'll do this at the Sunday hackathon since I believe
Te
Sounds good to me too. . .
any hope of convincing one of you to apply this (or a similar) patch
prior to the release:
https://issues.apache.org/struts/browse/WW-1458
Thanks,
David
Don Brown wrote:
I want to roll the Struts 2.0.1 release next weekend, October 8. A lot
of changes have gone
On 9/29/06, Don Brown <[EMAIL PROTECTED]> wrote:
Really? Dang it, I'm flying in on Saturday night, as I thought it was
Saturday and Sunday :/ Well, ok, I guess we'll roll 2.0.1 Monday then.
My flight is scheduled to arrive at 12:30 on Sunday, so if there's
connectivity, we could still do it o
Really? Dang it, I'm flying in on Saturday night, as I thought it was
Saturday and Sunday :/ Well, ok, I guess we'll roll 2.0.1 Monday then.
Don
Martin Cooper wrote:
On 9/29/06, Don Brown <[EMAIL PROTECTED]> wrote:
I want to roll the Struts 2.0.1 release next weekend, Octo
On 9/29/06, Don Brown <[EMAIL PROTECTED]> wrote:
I want to roll the Struts 2.0.1 release next weekend, October 8. A lot
of changes have gone into the code since 2.0.0 and I'd like to have a
solid release that people can check out after Ted and my talks.
I'm thinking we&#
I want to roll the Struts 2.0.1 release next weekend, October 8. A lot
of changes have gone into the code since 2.0.0 and I'd like to have a
solid release that people can check out after Ted and my talks.
I'm thinking we'll do this at the Sunday hackathon since I believe Ted
44 matches
Mail list logo
