On Sun, 04 Apr 2004 09:04:24 -0600, Joe Germuska wrote:
IMO, Struts datasource handling should be deprecated and removed.
It had it's place in the past but now Struts has no business
managing datasources; that's the containers job and most of
them do it better than Struts. I would like part
On Thu, 08 Apr 2004 18:41:25 -0700, Steve Raeburn wrote:
If I can figure out how to update the SF site, I'll update the list
this weekend.
Maybe the best thing would be to move the resources pages from SourceForge to the
Wiki. [Yes, I'm volunteering.:)] People are already recreating them there
Any thoughts on this one?
http://issues.apache.org/bugzilla/show_bug.cgi?id=28148
The current url validation in struts (validateUrl method in FieldChecks) only
uses the default url configuration options.
I am attaching a patch that will allow the following options to be set in the
The sad truth is that many teams that do use Struts cannot also use whatever other
goody they find on SourceForge or on some other open source host.
Many do have permission to use Struts, but getting permission to use another product
is a difficult task.
I believe we have an obligation to the
We might just follow the same general procedure we've used for Jakarta, the Commons,
and the Incubator.
* A Struts subproject is created in response to a proposal to the DEV list.
* The proposal must be made by a Struts Committer and name two other Struts Committers
who are willing to support
On Tue, 27 Apr 2004 11:39:03 -0400, Jason Pratt wrote:
I'll help out on that...
I love tiles, it has made my life a lot easier.
I've a feeling Matt ~wants~ to be interested too :) :)
You guys might try putting together a proposal that we post to the relevant parties.
On Mon, 26 Apr 2004
On Tue, 27 Apr 2004 22:31:20 -0700, Martin Cooper wrote:
I would hope that we would think *very* carefully before following
the same or similar procedures as these projects. These are all
umbrella projects, and the first two, at least, have clearly
demonstrated the problems with such projects.
On Sat, 15 May 2004 06:34:03 -0500, Vic Cekvenich wrote:
what are the plans for struts?
should you add active developers interested in keeping up?
Most of the future plans are on the roadmap. Once a stable Commons-Validator release
is available, we can cut 1.2.1 and then bring Struts-Chain
The best place to post a question like this is the Struts USER list.
Aside from those mentioned, there are three listed on the Struts Learning page.
http://jakarta.apache.org/struts/learning.html
which were chosen to demonstrate the different ways people use Struts when writing
applications.
: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Saturday, 15 May 2004 22:30
To: Struts Developers List
Subject: Re: struts future plans
On Sat, 15 May 2004 06:34:03 -0500, Vic Cekvenich wrote:
what are the plans for struts?
should you add active developers interested in keeping up?
Most
I believe it would be better to roll Struts 1.2.1 *before* the new releases of the
other Commons dependencies arrive.
I'd like to try rolling the Commons Validator 1.1.3 tomorrow, and then roll Struts
1.2.1 the next day.
If Commons Validator 1.1.3 then goes stable, Struts 1.2.1 would be in a
-collections. it
won't be long (one or two weeks only) before the releases have been
cut so i'd say that it's well worth the wait.
- robert
On 6 Jun 2004, at 13:30, Ted Husted wrote:
My schedule has stabilized again, and I can roll a release of
Commons-Validator tomorrow night
I'd suggest sticking to your original vision, Frank, and first do the simplest thing
that can possibly work.
Try it for 1.2.x as well as for the Struts-Chain request processor that is slated for
1.3.x, to be sure the approach will be forwardly compatible, and get it out there
where people can
-0400, Don Brown wrote:
Ok, I've posted patches (and unit tests) or suggested resolutions
for every bug, but I don't have commit privs yet so I'll let you
apply them. Now for Struts... :)
Don
Ted Husted wrote:
I read the problem descriptions, but I haven't actually *worked*
on any
The Commons Validator tickets and docs are up-to-date now. The next couple of days are
busy, but I can try to roll Validator 1.1.3 on Thursday, and then we could roll Struts
1.2.1 on Friday, if we can get the tickets squashed.
-Ted.
I just found out I've been patching and testing the wrong branch of the Commons
Validator component :(
Between this snafu and the issues with Struts Faces, perhaps the best thing would be
to roll back the changes that create a dependence on Commons Validator 1.1.3.
Do we know if there are any
these compatibility issues. maybe we could
head some of the user questions off by adding something to a page
somewhere or to the wiki.
- robert
On 7 Jun 2004, at 15:48, Ted Husted wrote:
We really should be making releases every few weeks anyway. So,
we can roll a release now and again when
On Wed, 09 Jun 2004 08:59:38 -0500, Joe Germuska wrote:
Someone needs to apply the patches to the VALIDATOR_1_1_2_BRANCH.
I'm not sure if Ted still has time to spend or not.
I've got some time scheduled to work on this Thursday night, or, if this isn't done,
setting up my credentials to sign a
They used to run between 4a and 5a PST. It's a batch job with the other nightlies, and
the precise time varied
On Thu, 10 Jun 2004 07:37:13 -0400, James Holmes wrote:
I checked the nightly builds directory this morning and there is no
struts nightly and no struts-faces nightly from last night.
like
directory moves and file renames that will be very useful in a reorganization. If we
are going to move Subversion, and it seems obvious that at some point we will, there
might be no better time.
-Ted.
On Tue, 22 Jun 2004 22:24:26 -0700 (PDT), Martin Cooper wrote:
On Mon, 21 Jun 2004, Ted
Jun 2004 21:38:14 -0400, Michael Rasmussen wrote:
Are they in head? Where are the problems?
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 8:40 PM
To: Struts Developers List
Subject: Re: Struts 1.2.1 release?
OK, the dependency ball
Oh well, I guess I'll look elsewhere for a framework.
If you can only use a framework that only bundles everything into one monothlitic
distribution, then yes you should. We tried that, and it is clearly not working. If
monolithic is the only way we could do things in the future, then I would
Validator 1.1.3 is an alpha release, so no, it should not be in a repository. It needs
to be installed manually. The Maven build should be returning the following URI, where
the JAR, distribution, and a Struts help page can be found.
http://www.apache.org/~husted/validator/v1.1.3
On Fri, 25
OK, we're down to 4 problem tickets. Two are against the validator, but patches are
not available. Two are against Struts-Faces, and could actually be skipped since
Struts-Faces would not be in the 1.2.1 release.
The release notes are updated, so if we can swat #29285 and #29796, we could try
So, if we can solve 29285, it looks like 1.2.1 would be ready to roll.
On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
OK, we're down to 4 problem tickets. Two are against the validator,
but patches are not available. Two are against Struts-Faces, and
could actually be skipped since
Since the LazyActionForm http://www.niallp.pwp.blueyonder.co.uk/ can be validated
like any other ActionForm, I don't see the basis for a technical objection. In the
documentation, we would want to *strongly* recommend using the validated version, and
remind people it is a *bad* practice to pass
I would agree that both the reality and perception is that patches for enhancements
are not often applied. But, throwing bodies at the problem is not the solution. People
have to *want* to work on a project like Struts. Really, really, want it, and be
willing to work for it. Candidates have to
?id=29285
Niall
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Thursday, July 01, 2004 11:44 PM
Subject: Re: Struts 1.2.1 release?
On Thu, 01 Jul 2004 22:19:39 +0100, Niall Pemberton wrote:
I agree.
Also it seems
Yes. Everything is reported to the DEV list, and so we could just change it again if
we disagreed.
-Ted.
On Sat, 03 Jul 2004 00:11:41 -0700, KUROSAKA Teruhiko wrote:
Hello again,
I closed this bug as it appears to be a simple mistake
in using Struts. But is it OK for non-comitters like
Just to answer the question about status, RESOLVED/FIXED means that we have applied
the patch or integrated the change.
So, yes, only a Committer should set the status to RESOLVED/FIXED, since Committers
are the only ones who can make changes to the codebase.
When you create the ticket, just
One of the best posts I've read on contributing to open source is one that Craig made
some time ago to the Tomcat list.
* http://jakarta.apache.org/site/contributing.html
In this post, Craig describes how committers evolve from users. As people use use
Struts, and find ways to improve it, they
On Thu, 01 Jul 2004 12:16:29 +0800, Shoaib wrote:
Can anybody please tell me , how to get these patches and these
patches are for version 1.1 or 1.2
They would be in the nightly build for the following day. (It's actually an
early-morning build.)
We're shipping the 1.2.x series now, and these
On Mon, 05 Jul 2004 07:50:09 -0700, Michael McGrady wrote:
So, what command line are we talking about?
Larry is assuming you are using Linux or have WinCVS's EXE available.
-T.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I imagine Craig has Struts-Faces compiling against 2.4 to make sure it stays in synch
with Tomcat 5.
But, the question is whether we want to mandate that Struts-Faces can only compile
against 2.3 (and not 2.4)? Or vice-versa. Or is there a way to write the class so it
compiles under either?
I
If you mean Apache projects don't require a uniform set of tools, that's correct. Many
people want to use the same CVS client or IDE to work on ASF code as they do at work,
so we don't prescribe which to use. Developers are invited to use whatever client
software they like, so long as it can
The idea is that we are doing them in tandem. We rolled Validator 1.1.3, so now can
roll Struts 1.2.1. Once a nounrelease/noun is rolled, then we decide whether to
verbrelease/verb it as beta or stable/General Availability. The votes are not
final, so we can vote them to beta and then to stable
On Tue, 06 Jul 2004 00:41:13 -0700, Craig McClanahan wrote:
Can whoever is going to be release manager for this confirm the version numbers?
Did you want to go ahead and do it, Craig?
There are other things I really should be doing right now, but no one else was
available.
Of course, if you
For 1.3.x, I'd like to reorganize the source tree so that it follows the Maven best
practices. I agree that we should still provide Ant build files too, so that Maven it
not required.
I think a good portion of the Committers and other developers would (and do) build
Struts with Maven locally,
I'm now testing, tagging, and rolling Struts 1.2.1. Please stand by :)
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The repository is tagged for STRUTS_1_2_1, and the release is available for review at
* http://www.apache.org/~husted/struts/v1.2.1
Once you have had a chance to review the release, please respond as to whether we
should
[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
On Thu, 08 Jul 2004 09:36:42 -0700, Craig McClanahan wrote:
Has anyone tested with 2.0.8? If so, I don't have any problem with
picking this up in a subsequent 1.2.x release. I'll update the
nightly build dependencies for tonight's run.
I did consider changing the dependency, but decided
Another approach to simplifying Struts would be to add more flexibility to the
struts-config. One patch I'd love to apply would provide the extends capability
found in Tiles to all the Struts elements. This would suck a lot of the redundant,
bug-generating redundancy [:)] out of larger modules.
into an app which in in another
dev cycle and so should be able to give it a pretty good workout.
Not quite sure what our threshold for GA is... a certain time
period? Sworn testimonials? A sign from above?
Joe
At 10:47 AM -0400 7/8/04, Ted Husted wrote:
The repository is tagged for STRUTS_1_2_1
If you wanted to start with the documentation, I noticed that there are some items in
the Newbie FAQ
* http://struts.apache.org/faqs/newbie.html
that could be integrated into the main documentation, particularly the ones regarding
ActionForms. It's mainly cut and paste from one XML doc to
For the routine stuff, I just use PuTTY and WinCVS.
* PuTTY provides the connection to the Apache server.
* WinCVS handles the CVS tasks (via PuTTY).
I also use the same setup for SourceForge projects, which is quite convenient.
I know many people like TortoiseCVS, which might be simplest of
the VOTE is declared?
Niall
PMC Binding Votes:
--
Don Brown: +1 GA or Beta
David Graham +1 Beta
Joe Germuska +1 Beta
James Homes +1 Beta
Steve Raeburn +1 Beta
Ted Husted (presume +1 but hasn't indicated a preference)
Other Non-Binding Votes
Bill has been of huge help to me personally and to many other Struts developers.
+1
On Sat, 10 Jul 2004 23:03:15 -0400, James Mitchell wrote:
I have known Bill for a few years and he is definitely committer
material. He has contributed in numerous ways to this community and
others. I owe him a
On Sun, 11 Jul 2004 11:50:57 +0100, Niall Pemberton wrote:
I assume this is PMC members only, but as you're posting this on
the dev list I guess its open for anyone to give their 2 cents.
It's true that only the PMC votes are binding, but votes and input from everyone is
always encouraged.
On Sun, 11 Jul 2004 08:09:24 -0400, Ted Husted wrote:
then I'd have to commit all those patches myself, and I honestly
don't have that kind of time anymore.
Oops, poor choice of words. Should have been then we'd have to commit all those
patches, and which of us has that kind of time right now
Done as to 1.2.1:
http://cvs.apache.org/dist/struts/v1.2.1
If we announce 1.2.1 (or 1.2.2 with ##27332) to the USER list as a Beta, does it have
to be signed and such?
I only ask since I still need to get setup for signing these things.
-Ted.
On Sat, 10 Jul 2004 20:54:02 -0700, Craig
On Sun, 11 Jul 2004 10:09:59 -0700, Martin Cooper wrote:
I can take care of that right now, if you want.
Sure. Let's just do it and move forward.
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
On Mon, 12 Jul 2004 14:41:32 -0700, Craig McClanahan wrote:
* Did we end up deciding to stick with CVS versus Subversion? I
know the infrastructure team would be happier if we switched to
svn ... I haven't
played with it enough to form an opinion on that yet.
I would be +1 for Subversion.
On Mon, 12 Jul 2004 17:44:40 -0500, Joe Germuska wrote:
Regarding CVS vs. SVN. I have zero SVN experience. I'm not
opposed to it, but it will be slower for me personally if we go
that route, as I'm starting at the bottom of the learning curve.
Subversion is designed (by teams like ours) to
On Mon, 12 Jul 2004 14:43:28 -0700 (PDT), Martin Cooper wrote:
I'm not completely sure I understand what you're proposing, but
here are a couple of points to bear in mind:
1) As we move out of the Jakarta repo into our own TLP repo, we
need to decide whether we want to ask infrastructure@ for
I got the opt- convention from Maverick. They have a core distribution, and then
several optional distributions for using the framework with different view
technologies. The idea is that all of these other distributions are optional. Of
course, Linux also uses /opt for packages that are not
On Tue, 13 Jul 2004 12:03:00 -0700 (PDT), Martin Cooper wrote:
As long as it's easy for me to check out the entire gorilla if
that's what I want. ;-)
But of course :)
That sounds nice in theory, but there are going to be cases where
we'll need to share code between different 'opt's, and
On Tue, 13 Jul 2004 13:01:05 -0500, Joe Germuska wrote:
struts-apps would not map to a single Maven artifact, I don't
think. Not if it maps to all of: struts-blank.war struts-
documentation.war struts-examples.war struts-mailreader.war
tiles-documentation.war
True. Kinda of the
On Tue, 13 Jul 2004 07:48:37 -0700, Martin Cooper wrote:
That would be excellent, Ted. That would let us all learn SVN as
well as play around with ideas without fear of messing things up
too badly. ;-)
If I could have found the time, I'd been thinking I wanted to do
something like this too,
On Sat, 17 Jul 2004 14:56:45 -0700, Craig McClanahan wrote:
* Separate modules for independently releaseable artifacts.
* Modules can depend on each other (i.e. pretty much all will
depend on core), but we should exercise caution if the dependency
tree gets deep ... complexity lurks here.
On Sun, 18 Jul 2004 13:15:45 -0700, Craig McClanahan wrote:
Personally, I want to stay focused on the code part first, and
would prefer someone more familiar with Maven and xml-html
transformations would focus on the site module.
What I'm thinking is that we should use an infrastructure
On Mon, 19 Jul 2004 16:48:35 -0700, Craig McClanahan wrote:
I was just following the usual conventions in the Subversion book,
and am not attached to the location (svn move and svn copy are *
sweet*). But first, a question ... if we are thinking about
actually keeping the end result, wouldn't it
On Mon, 19 Jul 2004 21:21:52 -0700, Martin Cooper wrote:
(BTW, that's something I think we should develop a policy on, so
that we're not seen as making arbitrary decisions in this area, but
that's another topic entirely.)
I think the decision would have to depend on who is going to maintain the
On Mon, 19 Jul 2004 21:07:14 -0700, Martin Cooper wrote:
One important question, though: Where are we doing 1.2.x
development / maintenance? Are we leaving that in CVS and splitting
off a new SVN repo for 2.0 development, or are we converting to SVN
lock, stock and barrel?
How about this:
* On
There are issues with using map-backed forms with the Struts Validator. Though, the
user list is the place to ask about how people are using things now. (It looks like
you might have the address for Struts User set to here too.)
My personal recommendation is to use finely-grained
We've only had a very few, very light tickets since the release of Struts 1.2.1 Beta.
I'd like to propose that we tag and release Struts 1.2.2 on Monday and post it for a
quality vote.
Please note that we can vote a release directly from Alpha to GA, if that's how we
feel about it.
-Ted.
Wheels on other carts started to squeak this week, and I haven't tagged or rolled
1.2.2 yet.
One thing I'd like to do first is to link our Acquiring page to the Apache mirroring
system, so that the distribution hooks up to the preferred place. I haven't looked
into how that is done yet. If
I don't think we're picky at this point. Either what Ant does or what Maven does would
be fine, robert.
-Ted.
On Thu, 29 Jul 2004 22:35:15 +0100, robert burrell donkin wrote:
On 28 Jul 2004, at 11:02, Ted Husted wrote:
snip
One thing I'd like to do first is to link our Acquiring page
.
- robert
On 29 Jul 2004, at 23:26, Ted Husted wrote:
I don't think we're picky at this point. Either what Ant does or
what Maven does would be fine, robert.
-Ted.
On Thu, 29 Jul 2004 22:35:15 +0100, robert burrell donkin wrote:
On 28 Jul 2004, at 11:02, Ted Husted wrote:
snip
One
: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Monday, August 09, 2004 11:56 PM
Subject: Re: Struts 1.2.2
I'll be tied up for some time yet. If anyone else can push this
along, please do.
-Ted.
On Wed, 28 Jul 2004 06:02:18 -0400, Ted Husted wrote
The release notes just need to be updated since the last time I did them, probably
last month. That much I should be able to squeeze in. They run back to Struts 1.1. If
1.2.2 goes GA, we can start fresh and incorporate the prior notes by reference.
On Wed, 11 Aug 2004 11:33:40 +0100, Niall
Yes, that's essentially what we've been doing. I run the Maven summary summary, and
then cut and paste the ones that matter under the various categories we've set up on
the Release Note page.
On Thu, 12 Aug 2004 02:31:23 -0400, Robert Leland wrote:
You could use what maven produces when you
I've been asking the likely suspects, Vic, but everyone pleads lack of time.
My own volunteer time is going into the iBATIS project now.
Apparently, Struts is good enough for now, and people who want more are moving on to
other pastures.
-Ted.
On Tue, 24 Aug 2004 07:57:07 -0500, Vic wrote:
On Tue, 24 Aug 2004 08:14:00 -0700, Michael McGrady wrote:
Heck, Jim, I am appreciative of all your efforts. I figure you owe
no one nothing. I would be glad to help, but, as Vic seems to
intimate, the entry into helping is not clear to those on the
outside unless you want to make a life of
Committership is a majority vote, so a -1 isn't a veto.
I've been asking the people you mentioned, Vic. They've been saying no.
-Ted.
On Tue, 24 Aug 2004 14:21:17 -0500, Vic wrote:
In 2001 I worked with others on validator and asked for the patches
to put in, and that was not applied. (my
On Tue, 24 Aug 2004 10:42:20 -0700, Michael McGrady wrote:
Thanks for all the info in this post, Ted, or is it Net? LOL ///8-
It's Apache :)
http://incubator.apache.org/projects/httpd-cli.html
-Ted.
-
To unsubscribe,
On Tue, 24 Aug 2004 12:34:50 -0700 (PDT), David Graham wrote:
I'm in a similar situation as Martin faced with more paid work than
one person has time for and still meaningfully contribute to
Struts. Personally, Struts does everything I need it to do so I've
been volunteering on validator and
It's better to submit these through Bugzilla, so they don't get lost.
http://struts.apache.org/using.html#Patches
-Ted.
On Tue, 24 Aug 2004 22:00:41 -0400, Dave Brosius wrote:
- Original Message -
From: Dave Brosius [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 24,
.
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED] Sent: Monday,
December 22, 2003 11:16 PM
Subject: Re: patch to make sure streams get closed
It's better to submit these through Bugzilla, so they don't get
lost.
http://struts.apache.org
On Wed, 25 Aug 2004 10:46:44 -0400, Mike Kienenberger wrote:
Bugzilla for the first time user is not trivial. Add to that the
possibility that he may have had Bugzilla lock up when he tried
to use it (that seemed to happen to me quite a bit -- I think it
turned out to require different IE
--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Wednesday, August 25, 2004 3:11 PM
Subject: Re: Struts 1.2.2 [was Patch
On Wed, 25 Aug 2004 20:01:54 -0700, Martin Cooper wrote:
It looks like signatures have not been created for the distribution
as uploaded to cvs.apache.org, so A3 isn't quite done yet. (Or perhaps
we should have had an A2.5 for this. ;)
It was my understanding that signatures are required for
for the votes to roll in?
--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Thursday, August 26, 2004 3:46 AM
Subject: Re
+1
On Wed, 25 Aug 2004 22:25:27 -0400, James Mitchell wrote:
I have finished rolling the 1.2.2 release.
The acquiring page has been updated with the 1.2.2 release.
http://struts.apache.org/acquiring.html
I am +1 for making this GA.
--
James Mitchell
Software Engineer / Open Source
On Mon, 30 Aug 2004 16:04:36 -0400, James Mitchell wrote:
I guess all the jakarta references will be changed when we go to
svn.
Yeah, I thought about renaming them, but since that's still where the CVS lives, it's
not inappropriate. :)
-Ted.
We forked the release notes at 1.1 to create release-notes-1.1.xml.
Since there hasn't be a GA release since, the notes since then are all in
release-notes.xml, which corresponds to
http://struts.apache.org/userGuide/release-notes.html.
There's mention there of notes for 1.2.1, but that's
On Tue, 31 Aug 2004 11:22:56 -0500, Joe Germuska wrote:
Perhaps we should have a similar justification for 2.3, but I guess
I feel like it's old enough now that just because is an OK reason.
Why 2.3?
(1) It is preferred platform of active Struts developers.
(2) It is needed for certain
One very good reason to stay with Bugzilla is that we often exchange tickets with
Jakarta Commons.
So, until Jakarta Commons changes to another system, I'm amending my previous +1 to -1.
Should Jakarta Commons ever change, then I would be in favor of migrating with them,
to retain
On Wed, 01 Sep 2004 08:11:06 +0100, Niall Pemberton wrote:
The disappointing thing from my point of view was that I put a
checklist for testing various JDK/Tomcat flavours in the Struts
1.2.2 release plan - but it was removed. If they had been left in
the plan then the JDK issues would have
We voted you in last month, Niall, and (I thought) I sent an announcement to the DEV
list.
Assuming you accept, let me know which email address do you want to use for the PMC
list?
(Joe, did you want yours changed?)
-Ted.
On Wed, 01 Sep 2004 10:00:24 +0100, Niall Pemberton wrote:
The user
On Wed, 01 Sep 2004 00:22:42 -0700, Martin Cooper wrote:
Saw that. I just volunteered as RM... ;-)
Do you just want to roll and test it with the infrastructure issues resolved.
Or, do we want to apply some of the new patches, update the roadmap, and so forth?
-Ted.
On Tue, 31 Aug 2004 17:49:27 -0500, Michael Rasmussen wrote:
Isn't the bugzilla installation a single instance for the entire
apache community? Can it be decided by struts to upgrade the
entire apache bugzilla site? Or is it just a struts instance?
It's a single instance. As it stands, we
On Thu, 02 Sep 2004 11:43:37 +0200, Anders Steinlein wrote:
Just want to throw in my voice here, as this is exactly what I've
been thinking. I'm very pleased with Struts and use it on a daily
basis and I would love to contribute, but I don't really have the
itches or time to fully read up on
On Wed, 01 Sep 2004 22:28:42 -0700 (PDT), Martin Cooper wrote:
* CVS freeze/tag date: Friday, September 3rd @ 6pm (Pacific time).
Following discussion on the list, did we want to make that the CVS freeze/tag/branch
date? Of course, we could always branch on the tag later too.
Once this release
On Thu, 02 Sep 2004 13:50:30 -0700, Martin Cooper wrote:
Do we want to call that 1.3.x or 2.0.x? I'm thinking that some
degree of revolution will happen in this next (2.3-based) version,
as well as some logical evolution. I haven't yet seen any proposed
advantages *to Struts future* listed for
OK, to sum up what people seem to be saying here:
[Struts 1.2.x]
* The minimums for 1.2.3 will remain Servlet 2.2
* We create a branch at the 1.2.3 tag, in case we need to make critical fixes to 1.2.x
later.
[Struts HEAD]
* For now, Struts HEAD can remain in evolutionary mode, but we will
On Fri, 03 Sep 2004 16:23:57 -0400, Don Brown wrote:
I propose we migrate our current CVS repository to Subversion as
soon as the infrastructure team is available to assist , giving at
least a week to ensure all outstanding CVS commits are made.
+1
On Fri, 03 Sep 2004 13:13:47 -0700, Craig
On Tue, 07 Sep 2004 04:11:42 +0100, Niall Pemberton wrote:
I have also committed a patch for Bug 31060 with the reasoning that
if we need to re-create the 1.2.3 release then we should also take
the opportunity to fix this bug as well:
If it were just a matter of patching the DTD's on the
On Tue, 07 Sep 2004 08:46:26 -0500, Joe Germuska wrote:
I don't know if there's a protocol about this, but actually, I
wasn't quite clear on why Martin was being tentative about
describing the release he cut as officially 1.2.3.
The build was officially named 1.2.3, but, as Martin says, it
I'm not using Struts in production myself right now, so I'm going to abstain from
voting in favor of them that do. :)
I do still plan to help support the release once it is out.
As to the voting in general ...
On Thu, 16 Sep 2004 08:09:18 -0500, Joe Germuska wrote:
I wouldn't veto GA, but I'm
On Sun, 10 Oct 2004 16:04:40 -0400, Mike Stanley wrote:
Another simple suggstion I would like to make (enhancement request) -
it would be extremely powerful to add the property support that
exists for plugin configuration, to action and request processors.
This can go along way for special
1 - 100 of 1977 matches
Mail list logo
