On Sat, 7 Jun 2003, Ted Husted wrote:
Date: Sat, 07 Jun 2003 16:55:07 -0400
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Status check?
Craig R. McClanahan wrote:
By the way, I uploaded
Vic Cekvenich wrote:
I downloaded and it apears to work with a sample app of mine, just
FYI.
Phil Steitz wrote:
Ted,
Don't know if this is useful, but I did the following successfully:
1. Hack build.xml to remove compile.library depends for tomcat, junit
test targets.
2. Replace contents of
I'm still play-testing the web apps against all three, but here's an
early warning:
Running the exercise app under Tomcat 3.3.1a
The logic-compare test kills container - nothing in log to indicate why.
This is a big test, so it may be rendering problem. (TC41 is OK)
Same result under NN and
moves, and
will catch on enough to displace CVS some day.
-Max
- Original Message -
From: David Graham [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, June 06, 2003 1:48 PM
Subject: Re: Status check?
It makes more sense to me to *not* tag the commons files with Struts
there intended to make it easier to test the same
app(s) in a variety of containers?
-Max
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Friday, June 06, 2003 3:39 PM
Subject: Re: Status check?
Martin Cooper wrote:
For the main
So, I tried it under Tomcat 3.3.1 (no a), with the same result. =:(
I had compiled the release under servlet 2.3, but I redid it under
servlet 2.2 with the same result.
I don't use cookies much, and off-hand I don't know if it's a problem
with the test, Tomcat, or Jasper. The other cats are
Craig R. McClanahan wrote:
The nightly directories get any file older than five days cleaned out --
and, because I'm not able to deal with getting them published in the time
I'm at JavaOne, that means a somewhere else or nothing policy is
important.
Understood and agreed. Making the s-f
Martin Cooper wrote:
You'll find everything ready to go at ~martinc/struts-legacy on cvs.a.o.
I've created the .asc signature files, and the .md5 digest files, but only
for the .tar.gz and .zip files, since we don't usually release the .tar
files. (They're only needed to produce the .tar.gz
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 08, 2003 4:37 AM
To: Struts Developers List
Subject: Re: Status check? - Houston we have a problem
I'm still play-testing the web apps against all three, but here's an
early warning:
Running
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 08, 2003 10:24 AM
To: 'Struts Developers List'
Subject: RE: Status check? - Houston we have a problem
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Sunday
Ted Husted wrote:
BUILD FAILED
file:C:/projects/Apache/jakarta/jakarta-struts/build.xml:308:
java.lang.IllegalM
onitorStateException: current thread not owner
Total time: 3 seconds
Any thoughts?
J2SE 1.3 compiles fine, and of course 1.4 is good, and I thought I had
1.2 working too, but now it
OK, the release-notes are updated. ]My, we have been busy little
beavers:-)]. There were a good number of refactoring and fixes, but no
new major changes aside from those stated. (Though, I'll need to add the
new deprecations to the What's Different list.
If there's anything else we've done
Ted Husted wrote:
OK, the release-notes are updated.
The page is not linked, but I uploaded it already.
http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc2.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I'm doing a cleanup pass over the release notes right now, fixing some
things and cleaning up the text in some places. Is it OK for me to go
ahead and check that in when I'm done, Ted?
--
Martin Cooper
On Sat, 7 Jun 2003, Ted Husted wrote:
OK, the release-notes are updated. ]My, we have been
On Sat, 7 Jun 2003, Ted Husted wrote:
Date: Sat, 07 Jun 2003 14:25:23 -0400
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Status check?
Yes, go ahead, Martin.
I made a couple of very minor
On Sat, 7 Jun 2003, Craig R. McClanahan wrote:
On Sat, 7 Jun 2003, Ted Husted wrote:
Date: Sat, 07 Jun 2003 14:25:23 -0400
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Status check
Martin Cooper wrote:
I'm actually in the middle of adding that now. ;-) I remember you asked me
a while ago to make sure we list the explicit versions we use.
The What's Included section seems like the logical place. My only
concern is that, because of the length of the RC/Beta Fixes section,
it's
On Sat, 7 Jun 2003, Ted Husted wrote:
Martin Cooper wrote:
I'm actually in the middle of adding that now. ;-) I remember you asked me
a while ago to make sure we list the explicit versions we use.
The What's Included section seems like the logical place. My only
concern is that,
Martin Cooper wrote:
Incidentally, I noticed that the installation page still references DBCP
and Pool, and the build file is still including those jars in the build.
We obviously need to fix those before the release. Let me know if you'd
like me to take care of either of those.
I'm trying to run
Craig R. McClanahan wrote:
By the way, I uploaded the new Struts-Faces integration library stuff (and
copied over the old one for legacy purposes) to a new directory:
http://jakarta.apache.org/builds/jakarta-struts/release/struts-faces/
I left a web server redirect in place so to that the old
On Sat, 7 Jun 2003, Ted Husted wrote:
Martin Cooper wrote:
http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases
I added the section on PGP 8.0 Freeware, since that's what I use, but you
can also use GPG, which I think is installed on daedalus. The MD5 tool is
definitely
On Sat, 7 Jun 2003, Ted Husted wrote:
Martin Cooper wrote:
You'll find everything ready to go at ~martinc/struts-legacy on
cvs.a.o. I've created the .asc signature files, and the .md5 digest
files, but only for the .tar.gz and .zip files, since we don't usually
release the .tar
SNIP:
Ted Husted wrote:
There's a
working candidate at http://cvs.apache.org/~husted/ - This is a preview
only - it is *not* the final RC! but it's what we want to test.)
I downloaded and it apears to work with a sample app of mine, just FYI.
.V
Ted Husted wrote:
Martin Cooper wrote:
You'll find everything ready to go at ~martinc/struts-legacy on
cvs.a.o. I've created the .asc signature files, and the .md5 digest
files, but only for the .tar.gz and .zip files, since we don't usually
release the .tar files. (They're only needed to
of RC2 before final?... (what's two more
weeks?... they'll fly by, I promise :)
Arron.
- Original Message -
From: David Graham [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:42 PM
Subject: RE: Status check?
Right, but what's the right amount of time
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:42 PM
Subject: RE: Status check?
Right, but what's the right amount of time to wait?
Craig suggested 2 weeks and I think that sounds good.
+1
--
James Mitchell
Software Developer/Struts Evangelist
http://www.struts
by, I promise :)
Arron.
- Original Message -
From: David Graham [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:42 PM
Subject: RE: Status check?
Right, but what's the right amount of time to wait?
Craig suggested 2 weeks
Our installation page says our dependency is J2SE 1.2 or later.
Does that mean I should compile the binary distribution under the latest
J2SE 1.2, or should I use the latest J2SE 1.4?
I'm installing 1.2 now, to at least be sure it still builds (as I
remember, the nightlies are building on
Martin Cooper wrote:
The tagging for the main Struts release will actually be a bit more
painful for RC2 since you can't just blanket-tag the Commons packages -
they'll have to be tagged individually to match the specific versions
we're bundling.
I can understand why we tagged the Commons packages
For Java 1.2 and 1.3, we need to have JAXP available to build the
distribution. The RI isn't distributed separately anymore, but is part
of the Web Services bundle.
http://java.sun.com/xml/jaxp/faq.html#jaxp-ri-latest
I tried pulling out the jaxp-api.jar, but that didn't seem to work.
Before
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Our installation page says our dependency is J2SE 1.2 or later.
Does that mean I should compile the binary distribution under the latest
J2SE 1.2, or should I use the latest J2SE 1.4?
I have been building the releases using
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Martin Cooper wrote:
The tagging for the main Struts release will actually be a bit more
painful for RC2 since you can't just blanket-tag the Commons packages -
they'll have to be tagged individually to match the specific
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 1:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Status check?
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Our installation page says our dependency is J2SE 1.2
Perhaps a -target 1.2 option should be specified on our javac
targets? I would guess the number of issues with down-compilation from
1.4 to 1.2 is very small, but if we have one in our code base, the
compiler won't tell us about it.
-Original Message-
From: Hajratwala, Nayan (N.)
Martin Cooper wrote:
I'll take care of tagging our dependencies once RC2 is out.
Hey, if setting CVS tags is something you like to do, more power to you,
brother =:)
But don't forget to tag ORO too, not to mention the jdbc2_0-stdext.jar
and Servlet JAR =:) We also have external dependencies on
Martin Cooper wrote:
As far as building and packaging go, you might want to take a look at the
'release' target I added to the main Struts build file. That really helps
with putting the binary and source uploads together.
Very nice work here, Martin. This target certainly simplifies things!
Just
Martin Cooper wrote:
I have been building the releases using J2SE 1.4 for some time now, and I
would recommend sticking with that. Going with 1.4 ensures we get the
benefits of the latest compiler improvements. The compatibility issue is
with the JVM rather than the compiler - we want to be able
It makes more sense to me to *not* tag the commons files with Struts. The
commons doesn't need to be notified every time Struts cuts a release. The
commons jars contain version information in their manifests so it would be
very easy to recreate an old Struts build by looking there.
David
Ted Husted wrote:
Just sorting out what I need to do to retrofit 1.2/1.3 with JAXP these
days, so I can confirm we still compile with the old guard =:0)
I downloaded the latest Web Services pack (I had an older version), and
at first the JAXP from that distribution seemed to work, but now for
Martin Cooper wrote:
For the main Struts release, the most time-consuming part is just testing
that everything works with all the supported containers (including all the
web apps).
So, I take it we would be satisfied with testing our sample applications
against the binary distribution (rather
If you're going to cross-compile, you really need to go whole-hog and
use the target, bootclass, and extdirs options. See:
http://java.sun.com/j2se/1.4.1/docs/tooldocs/solaris/javac.html#crosscomp-options
and:
http://java.sun.com/j2se/1.4.1/docs/tooldocs/solaris/javac.html#crosscomp-example
On Fri, 6 Jun 2003, David Graham wrote:
Date: Fri, 06 Jun 2003 14:48:13 -0600
From: David Graham [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Status check?
It makes more sense to me to *not* tag the commons files with Struts
On Sat, 31 May 2003, Martin Cooper wrote:
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Martin Cooper wrote:
Now, about the Struts 1.1 RC2 release. The problem is the staging
needed to get FileUpload out the door. It's currently at Beta 1, and
the code
Martin Cooper wrote:
OK, FileUpload 1.0 RC1 is out. I haven't done the announcement yet, or
updated the web site, but it's there.
The Tomcat build did indeed break, and interested parties can see the
resulting fun on commons-dev or tomcat-dev. ;-) Thanks to David and Joe
for their support.
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:25 PM
To: Struts Developers List
Subject: Re: Status check?
Martin Cooper wrote:
OK, FileUpload 1.0 RC1 is out. I haven't done the
announcement yet, or
updated the web site
2:25 PM
To: Struts Developers List
Subject: Re: Status check?
Martin Cooper wrote:
OK, FileUpload 1.0 RC1 is out. I haven't done the
announcement yet, or
updated the web site, but it's there.
The Tomcat build did indeed break, and interested parties
can see the
resulting fun
On Wed, 4 Jun 2003, Ted Husted wrote:
Date: Wed, 04 Jun 2003 14:25:15 -0400
From: Ted Husted [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Status check?
Martin Cooper wrote:
OK, FileUpload 1.0 RC1 is out
Right, but what's the right amount of time to wait?
James
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:34 PM
To: [EMAIL PROTECTED]
Subject: RE: Status check?
Setting release dates is not a good idea for many reasons.
IMO
Right, but what's the right amount of time to wait?
Craig suggested 2 weeks and I think that sounds good.
David
James
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:34 PM
To: [EMAIL PROTECTED]
Subject: RE: Status check?
Setting
Good for me too.
James
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:43 PM
To: [EMAIL PROTECTED]
Subject: RE: Status check?
Right, but what's the right amount of time to wait?
Craig suggested 2 weeks and I think that sounds
- Original Message -
From: David Graham [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:42 PM
Subject: RE: Status check?
Right, but what's the right amount of time to wait?
Craig suggested 2 weeks and I think that sounds good.
+1
--
James Mitchell
Ted Husted wrote:
Craig R. McClanahan wrote:
I do think we should say something like two weeks after RC2, barring
any major bugs so that we can encourage people to actually try RC2 in
that time frame.
June 15 would the be second anniversary of Struts 1.0 -- but I reckon
that's a might too
From: Ted Husted [mailto:[EMAIL PROTECTED]
So, pending advice to the contrary, I'll plan on putting 29
June 2003 in
the Release Plan (two years and two weeks after Struts 1.0).
Sounds very Lincoln-ian... Two years and two weeks ago, Craig McClanahan
brought forth upon the Java community
On Wed, 4 Jun 2003, James Turner wrote:
Sounds very Lincoln-ian... Two years and two weeks ago, Craig McClanahan
brought forth upon the Java community a new framework, conceived of MVC,
and devoted to the notion that all business logic should be treated
separate.
:-)
Advice to Craig:
If anyone had a mind to, it would be really great to have the Struts
News and Resources pages updated this week, before the next RC. There's
been a bunch of stuff announced on the list lately. (If not, I'll try to
do it before we go to final release.)
I'm still getting my head around the
On Tue, 3 Jun 2003, Ted Husted wrote:
If anyone had a mind to, it would be really great to have the Struts
News and Resources pages updated this week, before the next RC. There's
been a bunch of stuff announced on the list lately. (If not, I'll try to
do it before we go to final release.)
Martin,
I'm trying to release the struts-legacy package with our
GenericDataSource implementation. I'm working from the Commons
instructions (but substituting jakarta-struts where appropriate).
http://jakarta.apache.org/commons/releases.html
At step 5, it looks like I should log into
On Sun, 1 Jun 2003, Ted Husted wrote:
Martin,
I'm trying to release the struts-legacy package with our
GenericDataSource implementation. I'm working from the Commons
instructions (but substituting jakarta-struts where appropriate).
http://jakarta.apache.org/commons/releases.html
The
Martin Cooper wrote:
Now, about the Struts 1.1 RC2 release. The problem is the staging
needed to get FileUpload out the door. It's currently at Beta 1, and
the code base in CVS has some methods that have been deprecated since
Beta 1. The deprecated methods need to be removed before 1.0 Final,
Ted Husted [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Martin Cooper wrote:
Now, about the Struts 1.1 RC2 release. The problem is the staging
needed to get FileUpload out the door. It's currently at Beta 1, and
the code base in CVS has some methods that have been
So you're suggesting that I rip out the deprecated methods now, go for RC1,
and damn the torpedoes that the API is incompatible between Beta 1 and RC1,
and there was no warning (other than nightly builds)? You really think
that's OK?
On one hand, it seems rude to break the builds with not much
Martin Cooper wrote:
So you're suggesting that I rip out the deprecated methods now, go for RC1,
and damn the torpedoes that the API is incompatible between Beta 1 and RC1,
and there was no warning (other than nightly builds)? You really think
that's OK?
Gump builds for Tomcat and Turbine will
on is the final release of FileUpload, which
Martin is working on.
Can we get a status check on FileUpload? It would be mighty nice to get
RC2 out before JavaOne.
First, the FileUpload status. I have had some e-mail exchanges off-list
with the reporters of the two outstanding bugs. A partial
on.
Can we get a status check on FileUpload? It would be mighty nice to
get
RC2 out before JavaOne.
First, the FileUpload status. I have had some e-mail exchanges off-list
with the reporters of the two outstanding bugs. A partial solution
exists
for one of them, and, when completed, should actually
64 matches
Mail list logo
