On Wed, 24 Mar 2004 22:33:50 -0800 (PST), Martin Cooper wrote:
> I can probably do the RM thing for Validator if someone else
> (David?) can do the doc and release note updates. Just let me know
> when we're ready to roll and I can take it from there.
How about if we shoot for the
struts to use validator 1.1.1.
>
> I can probably do the RM thing for Validator if someone else (David?)
> can
> do the doc and release note updates. Just let me know when we're ready
> to
> roll and I can take it from there.
It looks like the RELEASE-NOTES.readme just point
This is really a "counting down to the 1.3.0 release" issue, but I've started on a
version of the MailReader application for Commons Chain. The idea being, instead of
using conventional Struts Actions, we can use Command and pass what's needed through a
Context. I setup the
n't be able to be RM to for Validator until Mid April, so we need
> a volunteer.
>
> Otherwise, we'll need to roll back the JavaScriptTag.java and
> validator-rules.xml in struts to use validator 1.1.1.
I can probably do the RM thing for Validator if someone else (David?) can
do t
> -Original Message-
> Do we want to wait for a Validator 1.1.2, or roll it with 1.1.1?
I just fixed a show stopper bug today in validator in CVS and made an accompaning
change in Struts CVS.
I won't be able to be RM to for Validator until Mid April, so we need
a volunteer.
Otherwise, w
ailto:[EMAIL PROTECTED]
> > >> Well, did-ja have anything to add to the list, Matt? :)
> > >
> > > Nope - release, release!!
> >
> > The ones we have are resolvable, but, I'm thinking Martin has something
> > up his sleeve yet ...
> >
> &
On Wed, 24 Mar 2004 12:11:01 -0800 (PST), Martin Cooper wrote:
> Do we want to wait for a Validator 1.1.2, or roll it with 1.1.1?
Well, we can't roll it with 1.1.1, since the report says the client validations won't
work without the nightly build.
It would be cool if we could roll Validator 1.1.
t would be nice to resolve the issue with the Cactus
> > tests not stopping properly on Tomcat 5.0, but I can live without
> > that if necessary.
>
> Well, if we get the problem tickets down to zero, and I update the release notes
> again, would we be up for rolling 1.2.1 this wee
h it is no problem IMO.
David
>
> > -Original Message-
> > From: David Graham [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, March 24, 2004 12:55 PM
> > To: Struts Developers List
> > Subject: Re: Counting down to the 1.2.1 release (was RE: Making Struts
> &
5 PM
> To: Struts Developers List
> Subject: Re: Counting down to the 1.2.1 release (was RE: Making Struts
> Build Easier)
>
>
>
> --- Ted Husted <[EMAIL PROTECTED]> wrote:
> > On Wed, 24 Mar 2004 09:03:46 -0700, Matt Raible wrote:
> > >> -Origin
ts not stopping properly on Tomcat 5.0, but I can live without
> that if necessary.
Well, if we get the problem tickets down to zero, and I update the release notes
again, would we be up for rolling 1.2.1 this weekend?
-Ted.
--
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> On Wed, 24 Mar 2004 09:03:46 -0700, Matt Raible wrote:
> >> -Original Message-
> >> From: Ted Husted [mailto:[EMAIL PROTECTED]
> >> Well, did-ja have anything to add to the list, Matt? :)
> >
> >
On Wed, 24 Mar 2004 09:03:46 -0700, Matt Raible wrote:
>> -Original Message-
>> From: Ted Husted [mailto:[EMAIL PROTECTED]
>> Well, did-ja have anything to add to the list, Matt? :)
>
> Nope - release, release!!
The ones we have are resolvable, but, I'm thi
husted 2004/03/22 17:02:30
Modified:doc/userGuide release-notes.xml
Log:
Update release notes.
Revision ChangesPath
1.50 +28 -2 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
David Graham,
I finished 3 minutes ahead of my estimated time. :) Unfortunately, it's
taking forever (30 minutes so far) to upload the patch file, which is
just shy of 2 megs. Would it speed things up any to send you a copy
directly, while it's uploading? I thought I'd ask since we're on a
s Developers List'
> Subject: Re: [VOTE] 1.2.0 Release Plan
>
> I woke up earlier than planned (I'm on a strange sleep schedule) and
> Robert Leland got me a copy of the tools, which saved me a bunch of time
> since my own tool was only 40% done. I used the java one,
Subject: Re: [VOTE] 1.2.0 Release Plan
David Karr emailed me, so I'll take care of the licenses this weekend.
I have a social engagement today, so I'll take care of it on sunday.
Thanks for doing this, Paul. One caveat: The tag/freeze for 1.2.0 happens
tonight at midnight my time. Sinc
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 21, 2004 8:10 AM
> To: Struts Developers List
> Subject: Re: [VOTE] 1.2.0 Release Plan
>
>
>
> > -Original Message-
> > From: Karr, Davi
> -Original Message-
> From: Joe Germuska [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 20, 2004 11:50 AM
> To: Struts Developers List
> Subject: Re: [VOTE] 1.2.0 Release Plan
>
>
> > > Just a few things:
> >>
> >> * What about the
> -Original Message-
> From: Paul Sundling [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 21, 2004 7:52 AM
> To: Struts Developers List
> Subject: Re: [VOTE] 1.2.0 Release Plan
>
>
> David Karr emailed me, so I'll take care of the licenses this weekend.
> -Original Message-
> From: Karr, David [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 21, 2004 12:46 AM
> To: 'Struts Developers List'
> Subject: RE: [VOTE] 1.2.0 Release Plan
>
> Does this involve changing the file header comment to replace the
ting license with the new license? That's something that I can
> >>>>relatively easily script in elisp macros. If someone can confirm
> >>>>
> >>>>
> >>that's
> >>
> >>
> >>>>all this is
exactly what needs to change, I can get that
done this weekend.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
exactly what needs to change, I can get that
> >>done this weekend.
> >>
> >>-Original Message-
> >>From: Joe Germuska [mailto:[EMAIL PROTECTED]
> >>Sent: Friday, February 20, 2004 12:12 PM
> >>To: Struts Developers List
> >>Su
end.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
> Just a few things:
* What about the new Apache license?
y, February 20, 2004 12:12 PM
> To: Struts Developers List
> Subject: Re: [VOTE] 1.2.0 Release Plan
>
>
> At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
> >> > Just a few things:
> >>>
> >>> * What about the new Apache license? Technically, it doe
at
done this weekend.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
> Just a few things:
* What about the new Apac
is weekend.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
>> > Just a few things:
>>>
>>>
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
> Just a few things:
* What about the new Apache license? Technically, it doesn't need to
change if we release before March 1st, but we're mighty close to that,
so
> perhaps we should switch now?
+1 from me too; wasn't someon
> Just a few things:
* What about the new Apache license? Technically, it doesn't need to
change if we release before March 1st, but we're mighty close to that,
so
> perhaps we should switch now?
+1 from me too; wasn't someone offering to do it a few weeks ago?
At this
> contrib
Personally, I've been defining what is released by what is generated by the release
target. :)
For Struts 1.1, Struts-El was released coincident with the Struts 1.1 release, but
they were separate events. If someone wants to also roll a struts-el release, or
struts-jsf
--- Martin Cooper <[EMAIL PROTECTED]> wrote:
> On Fri, 20 Feb 2004, Ted Husted wrote:
>
> > Assuming it was all right with everyone, I'm setting the freeze date
> for 1.2.0 for tomorrow (Saturday) night.
> >
> > I'm updating the release plan. There ar
On Fri, 20 Feb 2004, Ted Husted wrote:
> Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for
> tomorrow (Saturday) night.
>
> I'm updating the release plan. There are still a lot of enhancement patches that we
> haven't applied,
At 9:37 AM -0500 2/20/04, Ted Husted wrote:
Assuming it was all right with everyone, I'm setting the freeze date
for 1.2.0 for tomorrow (Saturday) night.
I'm updating the release plan. There are still a lot of enhancement
patches that we haven't applied, but I think those can wai
husted 2004/02/20 09:03:20
Modified:doc project.xml releases.xml status.xml
doc/proposals release-plan_1_2_0.xml
Log:
Correct hyperlinks.
Revision ChangesPath
1.47 +4 -4 jakarta-struts/doc/project.xml
Index: project.xml
husted 2004/02/20 08:35:17
Modified:doc/userGuide release-notes.xml
Log:
Update release notes.
Revision ChangesPath
1.49 +3 -0 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2004/02/20 06:41:23
Modified:doc/proposals release-plan_1_2_0.xml
Log:
Revise date, postpone remaining patches.
Revision ChangesPath
1.8 +5 -7 jakarta-struts/doc/proposals/release-plan_1_2_0.xml
Index: release-plan_1_2_0.xml
Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for
tomorrow (Saturday) night.
I'm updating the release plan. There are still a lot of enhancement patches that we
haven't applied, but I think those can wait for later in the 1.2.x series. I do i
husted 2004/02/19 13:09:45
Modified:doc/userGuide release-notes.xml
Log:
Update release notes.
Revision ChangesPath
1.48 +30 -1 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2004/02/19 12:38:37
Modified:doc/userGuide release-notes.xml
Log:
Add module blurb; grammar/markup.
Revision ChangesPath
1.47 +83 -80jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2004/01/09 20:20:19
Modified:doc/userGuide release-notes.xml
Log:
Update release notes.
Revision ChangesPath
1.45 +172 -121 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
rleland 2004/01/08 09:13:01
Modified:xdocs/proposals release-plan-1.0b1.xml
Log:
Remove references to nagoya
and use issues and mail-archive instead.
Also sync doc & xdocs content
Revision ChangesPath
1.2 +2 -2 jakarta-struts/xdocs/proposals/release-
rleland 2004/01/05 21:49:41
Modified:.project.xml
contrib project.xml
doc learning.xml project.xml using.xml
doc/proposals release-plan-1.1b1.xml release-plan-1.1b2.xml
xdocslearning.xml navigation.xml
husted 2003/12/30 16:05:38
Modified:doc/userGuide release-notes.xml
Log:
Update release notes.
Revision ChangesPath
1.44 +17 -5 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
On Wed, 24 Dec 2003, Joe Germuska wrote:
> At 9:38 AM -0500 12/22/03, Robert Leland wrote:
> >I believe Joe said though all unit test ran they **didn't** all
> >pass, I believe it was like 66%
> >passed.
>
> Hi, all... I've been at my in-laws for the holidays and have
> intermittent net access.
>
At 9:38 AM -0500 12/22/03, Robert Leland wrote:
I believe Joe said though all unit test ran they **didn't** all
pass, I believe it was like 66%
passed.
Hi, all... I've been at my in-laws for the holidays and have
intermittent net access.
I turned out my major ant/cactus problem was that Ant was
I am now testing nightly and sample wars for what it's worth.
All wars work (once over lightly).
Somone did a nice job on localizing validation war.
bP works (which uses jstl 1.1, struts menu 2.1, etc.)
-Validation example complains in console about
-I wish most excetions were logged w/ e.getCua
Robert Leland wrote:
Ted Husted wrote:
OK, here's what we have
I would say release, we are using a x.y.z numbering scheme.
Noteing in the limited release that this should be considered an Alpha
until further testing says otherwise. Also to ask others not to announce
this on other
Ted Husted wrote:
OK, here's what we have
I would say release, we are using a x.y.z numbering scheme.
Noteing in the limited release that this should be considered an Alpha
until further testing says otherwise. Also to ask others not to announce
this on other lists
until it has been voted
I haven't had a chance to catch up completely, but the outage this weekend
suggests an after-Christmas 1.2.0 release, unfortunately - at least, if I
need to be involved. (If not, great - go for it!)
--
Martin Cooper
On Sun, 21 Dec 2003, Ted Husted wrote:
> OK, here's what we have
OK, here's what we have
* Release notes updated
* Issues w/o solutions marked LATER
* Webapps tested on TC 4.1 (one issue)
* JUnit tests run
In the Validator example, we're suppose to be able to change selected
validations for a county just by overriding a form in a formset. This
do
David Graham wrote:
--- Ted Husted <[EMAIL PROTECTED]> wrote:
So, there were a few more outstanding reports that I thought we would
have.
http://tinyurl.com/ysx3x
Notice that 12 of the 29 bugs are custom tag related proving once again
how badly we need to move them into their own distro.
Post 1.
dn't start making up new definitions of "enhancement" just to
accomodate our release schedule.
> (2) mark unresolved problem reports LATER (like before)
+1 on marking as LATER.
> (3) change the release plan so we can leave them open
> (4) forgo the release indefinitely
&g
without proposed solutions "enhancements"
(2) mark unresolved problem reports LATER (like before)
(3) change the release plan so we can leave them open
(4) forgo the release indefinitely
On a related topic, would anyone call any of these "showstoppers".
-Ted.
Ted Husted wrote:
I
Ted Husted wrote:
If we use the current Validator 1.1.1 JAR, and it becomes the final
release, then we could vote on whether Struts 1.2.0 can also be a
"final" or "General Availability" release.
If you recall I believe we came to consensus on struts-dev that
Validator can
+ 1 on the release plan...
Note that I've left room in the release plan for the idea of
multiple managers. If someone were up for sheparding the tests,
especially the example application testing, I'd welcome the help.
I may as well take this moment to fess up to my remedial status
On Tue, 16 Dec 2003, Ted Husted wrote:
+1
> I've amended the date on the (now venerable) 1.2.0 release plan for this
> weekend.
>
> http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html
>
> I believe the release notes are in good shape now. I already marche
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> The mean number of milestones for a Jakarta "stable" release seems to be
>
> five or six. So, it would not be unusual for us to get 1.2.4 before
> hitting a "General Availability" grade.
That could be because
If we use the current Validator 1.1.1 JAR, and it becomes the final
release, then we could vote on whether Struts 1.2.0 can also be a
"final" or "General Availability" release.
If this Validator 1.1.1 JAR does not make final, then the best we could
do is mark ours would be
Clarifying the voting guidelines is an active thread on the PMC list, so
we might just want to muddle along best we can for now. Regardless of
what we do for 1.2.1, we have called for a vote on a release plan for
1.2.0. The plan does call for a vote before classifying the Alpha as a
Beta or
Were we still planning on using Validator 1.1.1 when it is released ?
It's getting a little confusing, since I removed it, and called
for a release Vote. The vote isn't scheduled to complete until
Sunday Noon. And Struts source will be frozed at Saturday Midni
ig R. McClanahan> Quoting Martin Cooper <[EMAIL PROTECTED]>:
>
> > The issue isn't so much with voting on the relesae plan, but voting on the
> > release itself. As you say, the HTTPD rules say that anyone can create a
> > release. We're not HTTPD, though, and th
Quoting Martin Cooper <[EMAIL PROTECTED]>:
> The issue isn't so much with voting on the relesae plan, but voting on the
> release itself. As you say, the HTTPD rules say that anyone can create a
> release. We're not HTTPD, though, and the Jakarta rules are different. A
+1
> -Original Message-
> From: Ted Husted [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 16, 2003 05:48 PM
> To: 'Struts Developers List'
> Subject: [VOTE] 1.2.0 Release Plan
>
> I've amended the date on the (now venerable) 1.2.0 release p
The issue isn't so much with voting on the relesae plan, but voting on the
release itself. As you say, the HTTPD rules say that anyone can create a
release. We're not HTTPD, though, and the Jakarta rules are different. As
long as we're part of Jakarta, we need to abide by the Jakart
With this proposal, I took a middle ground. The initial minor release
(x.x.0) in a series called for a vote on a plan, but a plan would be
optional for additional releases in the same series (1.2.1, 1.2.2, ...).
So, we wouldn't have to vote on a plan again until we get to 1.3.0 or
2.0.0.
ar, the Jakarta rules require a vote, while the HTTPD rules do
not. I suspect that this vote may be sufficient, but I'll check when I get
a chance.
--
Martin Cooper
On Tue, 16 Dec 2003, Ted Husted wrote:
> I've amended the date on the (now venerable) 1.2.0 release plan fo
Ted Husted wrote:
. If someone were up for sheparding the tests, especially the
example application testing,
If testing example apps, means not much more than see if the war files
work and browse it, I will do it. (of course some of them had problems
before, like tiles example, but not sure wh
+1
David
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> I've amended the date on the (now venerable) 1.2.0 release plan for this
>
> weekend.
>
> http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html
>
> I believe the release notes are in g
I've amended the date on the (now venerable) 1.2.0 release plan for this
weekend.
http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html
I believe the release notes are in good shape now. I already marched
through most of the stale 1.0/1.1 tickets, and can mop up the re
martinc 2003/12/16 09:13:57
Modified:doc/proposals release-plan_1_2_0.xml
Log:
I can help.
Revision ChangesPath
1.7 +2 -2 jakarta-struts/doc/proposals/release-plan_1_2_0.xml
Index: release-plan_1_2_0.xml
husted 2003/12/16 09:07:56
Modified:doc/proposals release-plan_1_2_0.xml
Log:
Update release plan
Revision ChangesPath
1.6 +3 -3 jakarta-struts/doc/proposals/release-plan_1_2_0.xml
Index: release-plan_1_2_0.xml
I'll be out of town over the weekend and may not be able to get my mail.
If Commons Validator 1.1.1 rolls, and someone wants to do the same with
our 1.2.0, that would be fine with me. :)
-Ted.
-
To unsubscribe, e-mail: [EMAIL
husted 2003/12/11 19:20:53
Modified:doc project.xml status.xml
doc/userGuide building_controller.xml configuration.xml
installation.xml introduction.xml release-notes.xml
Log:
Minor tweaks.
Revision ChangesPath
1.44 +0 -4
husted 2003/12/11 12:37:26
Modified:doc/userGuide release-notes.xml
Log:
Through today.
Revision ChangesPath
1.42 +18 -20jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2003/12/11 12:24:54
Modified:doc/userGuide release-notes.xml
Log:
Through today.
Revision ChangesPath
1.41 +39 -31jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2003/12/11 09:54:31
Modified:doc/userGuide release-notes.xml
Log:
Through September.
Revision ChangesPath
1.40 +189 -57 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2003/12/11 04:26:09
Modified:doc/userGuide release-notes.xml
Log:
Start "What's New" section.
Revision ChangesPath
1.39 +78 -61jakarta-struts/doc/userGuide/release-notes.xml
Index: re
husted 2003/12/10 13:12:06
Modified:doc/userGuide release-notes.xml
Log:
Additional updates (through 07/31 now).
Revision ChangesPath
1.38 +68 -11jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2003/12/10 12:13:42
Modified:doc/userGuide release-notes.xml
Log:
Additional updates
Revision ChangesPath
1.37 +69 -45jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2003/12/09 17:02:25
Modified:doc/userGuide release-notes.xml
Log:
+ apply HTML Tidy -xml -i -m -wrap 0
Revision ChangesPath
1.36 +184 -219 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
husted 2003/12/09 16:57:50
Modified:doc/userGuide release-notes.xml
Log:
+ Streamline release note format in preparation for 1.2.x updates.
Revision ChangesPath
1.35 +145 -276 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
Steve Raeburn wrote:
> You can reduce the range that is checked for changes using:
> maven.changelog.range in project.properties
> It's currently set to 180 days (~6 months)
I wanted to get six-months wworth first, so I could archive enough to
get us past the 1.1 release, but I hav
y are up
to date then cut a release. There were a couple of good suggestions in
Bugzilla that David fielded
but those could wait for a 1.1.2 release.
-Ted.
-Rob
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
s Developers List
> Subject: Re: When is the next release?
>
>
> Robert Leland wrote:
> > Maven already creates a changelog for struts when a
> site:generate is
> > performed.
>
> Yes, in the end, that's what I did. Had to munge it a bit to
> agree with
> our s
makes for a big page. I'm thinking we can
archive one-month blocks and link backward from the current month.
My own immediate plans are to segment the changelog into one-month
blocks, update the release notes with the appropriate high-level bullets
(based on a review of the changelo
gzilla/show_bug.cgi?id=25125
Violation of JSP spec: release() method and pageContext + parent
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=25125
Violation of JSP spec: release() method and pageContext + parent
Summary: Violation of JSP spec: release() method and pageContext
+ parent
Product: Struts
Version: 1.1 Final
Platform: Other
OS/Version:
Ted Husted wrote:
Craig R. McClanahan wrote:
Another thing Remy does for Tomcat (which I *really* appreciate) is
keeps
a running change log (summary, not detailed) in the release notes for
each
version. That way, everyone can get a quick summary of what's changed.
So, I'm working
Craig R. McClanahan wrote:
Another thing Remy does for Tomcat (which I *really* appreciate) is keeps
a running change log (summary, not detailed) in the release notes for
each
version. That way, everyone can get a quick summary of what's changed.
Ted Husted wrote:
So, I'm working on on
Craig R. McClanahan wrote:
Another thing Remy does for Tomcat (which I *really* appreciate) is keeps
a running change log (summary, not detailed) in the release notes for each
version. That way, everyone can get a quick summary of what's changed.
So, I'm working on one of these now for
gzilla/show_bug.cgi?id=23523
Improper use of release() method in
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
martinc 2003/11/27 15:01:22
Modified:.README build-all-clean.bat.sample
contrib/struts-chain README.txt
contrib/struts-faces README.txt
doc/userGuide release-notes.xml
Log:
Document that Ant 1.5.2 or above is required to build
I am new to Slide. I wanted to know whether Slide is an ongoing project or
has it been shelved, since a friend of mine told me that Slide project
stopped sometime in 2001. From the Slide home page I am further confused,
since the last news (at http://jakarta.apache.org/slide/news.html ) is
posted o
gzilla/show_bug.cgi?id=23523
Improper use of release() method in
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|Improper use of release() |Improper use of r
gzilla/show_bug.cgi?id=23523
Improper use of release() method in custom tags (e.g. )
Summary: Improper use of release() method in custom tags (e.g.
)
Product: Struts
Version: 1.1 Final
Platform: All
OS/Version: All
Statu
rleland 2003/09/28 19:49:18
Modified:.build.properties.sample build.xml
doc/userGuide release-notes.xml
Log:
Update version of validator required in Docs.
Also, back in August we had talked about
making Struts depend on the latest stable releases:
so
release-notes-1.1.xml
Log:
Routine updates.
Revision ChangesPath
1.43 +22 -4 jakarta-struts/doc/status.xml
Index: status.xml
===
RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
rleland 2003/08/29 20:57:45
Modified:doc/userGuide release-notes.xml
Log:
Document Resource additions
Revision ChangesPath
1.30 +1 -0 jakarta-struts/doc/userGuide/release-notes.xml
Index: release-notes.xml
Robert Leland wrote:
> Shall we move to Validator 1.1.0, for 1.2.0 ?
If it makes it from Alpha to GA in time, and it's a drop-in replacement,
then it would be OK with me =:0)
Though, I'd like to get out at least one 1.2.x point release before
doing anything drastic, like migrati
1 - 100 of 562 matches
Mail list logo
