You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Mindbridge <mi...@yahoo.com> on 2003/11/12 19:50:07 UTC
versions
Hi,
I would like to raise this question both because there is expressed interest in it on the user list and because there are a number of open bugs dependent on the resoltion. The question is about the precise versions of the JDK and the Servlet API that Tapestry supports.
There are two similar bugs related on this topic:
24393 No JVM requirements mentioned in docs
http://issues.apache.org/bugzilla/show_bug.cgi?id=24393
and
24394 Public jvm version requirements policy
http://issues.apache.org/bugzilla/show_bug.cgi?id=24394
This has two aspects. One is where in the docs the Tapestry requirements should be listed. Here is what I suggest:
- An additional section under Introduction in the User's Guide that details clearly the requirements (see below)
- An additional section under Development Standards in the Contributors guide, referring to procedures for verifying the compatibility as described in the User's Guide (I know I am not always doing that)
The second aspect is what exactly the requirements are. We have discussed this before, so here is a brief summary:
1) JDK 1.2.2
Tapestry compiles under JDK 1.2.2 and runs fine according to a number of user accounts.
One little problem I had was that I was unable to run the JUnit tests under 1.2.2 and hence I couldn't be absolutely sure. (getting weird monitor exceptions). Has anyone had a better luck?
2) JDK 1.3
Again, compiles under JDK 1.3, runs fine, and JUnit tests can now be run there fine to verify compatibility.
One little issue -- in order for Tapestry, JUnit tests, etc. to run under 1.3 and 1.2.2, the Xerces libraries need to be present in the classpath. This is also described in this bug:
20253 JUnit XML tests broken under JDK with no XML parser (eg. 1.3)
http://issues.apache.org/bugzilla/show_bug.cgi?id=20253
Since some sort of an XML parser is usually provided by the servlet containers, this is not normally a sore thumb, but it will be good to know what jars are normally needed, and what is the minimum versions of those jars that is needed for Tapestry to run properly. Personally, I have always used the latest version of Xerces with all of its jars, and I have no idea what the minimum versions or what the required jars are. Does anyone have more experience here?
3) JDK 1.4
No issues there
4) Servlet API 2.2
Tapestry does NOT compile against Servlet API 2.2, BUT runs fine with it now. JUnit tests run fine.
5) Servlet API 2.3
No issues. Compilation, running, and junit tests are fine.
Any corrections to this summary?
There is one more thing and it is related to the followng bug:
21871 junit.jar needed to build junit subproject, but not included or mentioned anywhere
http://issues.apache.org/bugzilla/show_bug.cgi?id=21871
Is JUnit's license incompatible with the ASF one? I presume it is, since Howard did a rather extensive research about it while we were in incubation, but I would like to ask just in case...
Best regards,
-mb
Re: versions
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Wednesday, November 12, 2003, at 01:50 PM, Mindbridge wrote:
> 21871 junit.jar needed to build junit subproject, but not included or
> mentioned anywhere
> http://issues.apache.org/bugzilla/show_bug.cgi?id=21871
>
> Is JUnit's license incompatible with the ASF one? I presume it is,
> since Howard did a rather extensive research about it while we were in
> incubation, but I would like to ask just in case...
junit.jar really needs to be in ANT_HOME/lib for the <junit> task to
function properly, so you can pretty much assume that it is already
there and refer to it in the build file as ${ant.home}/lib/junit.jar.
If it isn't there, then tests aren't going to work anyway.
I code my build files to assume it's there.
As for it being incompatible? I doubt it... it is checked into other
ASF repositories (Ant's for example). But again, I would just assume
that it is in ANT_HOME/lib.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: versions
Posted by David Solis <ds...@legosoft.com.mx>.
> -----Original Message-----
> From: Mindbridge [mailto:mindbridgeweb@yahoo.com]
> Sent: Wednesday, November 12, 2003 12:50 PM
> To: Tapestry development
> Subject: versions
>
> Hi,
>
> I would like to raise this question both because there is expressed
> interest in it on the user list and because there are a number of open
> bugs dependent on the resoltion. The question is about the precise
> versions of the JDK and the Servlet API that Tapestry supports.
>
> There are two similar bugs related on this topic:
>
> 24393 No JVM requirements mentioned in docs
> http://issues.apache.org/bugzilla/show_bug.cgi?id=24393
>
> and
>
> 24394 Public jvm version requirements policy
> http://issues.apache.org/bugzilla/show_bug.cgi?id=24394
>
> This has two aspects. One is where in the docs the Tapestry
requirements
> should be listed. Here is what I suggest:
>
> - An additional section under Introduction in the User's Guide that
> details clearly the requirements (see below)
>
> - An additional section under Development Standards in the
Contributors
> guide, referring to procedures for verifying the compatibility as
> described in the User's Guide (I know I am not always doing that)
>
>
Agree.
> The second aspect is what exactly the requirements are. We have
discussed
> this before, so here is a brief summary:
>
> 1) JDK 1.2.2
> Tapestry compiles under JDK 1.2.2 and runs fine according to a number
of
> user accounts.
> One little problem I had was that I was unable to run the JUnit tests
> under 1.2.2 and hence I couldn't be absolutely sure. (getting weird
> monitor exceptions). Has anyone had a better luck?
>
What is the reason to have Tapestry running on JDK 1.2.2?
> 2) JDK 1.3
> Again, compiles under JDK 1.3, runs fine, and JUnit tests can now be
run
> there fine to verify compatibility.
>
> One little issue -- in order for Tapestry, JUnit tests, etc. to run
under
> 1.3 and 1.2.2, the Xerces libraries need to be present in the
classpath.
> This is also described in this bug:
>
> 20253 JUnit XML tests broken under JDK with no XML parser (eg. 1.3)
> http://issues.apache.org/bugzilla/show_bug.cgi?id=20253
>
> Since some sort of an XML parser is usually provided by the servlet
> containers, this is not normally a sore thumb, but it will be good to
know
> what jars are normally needed, and what is the minimum versions of
those
> jars that is needed for Tapestry to run properly. Personally, I have
> always used the latest version of Xerces with all of its jars, and I
have
> no idea what the minimum versions or what the required jars are. Does
> anyone have more experience here?
>
> 3) JDK 1.4
> No issues there
>
> 4) Servlet API 2.2
> Tapestry does NOT compile against Servlet API 2.2, BUT runs fine with
it
> now. JUnit tests run fine.
>
> 5) Servlet API 2.3
> No issues. Compilation, running, and junit tests are fine.
>
>
> Any corrections to this summary?
>
Excellent summary.
>
> There is one more thing and it is related to the followng bug:
>
> 21871 junit.jar needed to build junit subproject, but not included or
> mentioned anywhere
> http://issues.apache.org/bugzilla/show_bug.cgi?id=21871
>
> Is JUnit's license incompatible with the ASF one? I presume it is,
since
> Howard did a rather extensive research about it while we were in
> incubation, but I would like to ask just in case...
>
>
Who knows? JUnit is included in lucene and ojb repositories. JUnit is
released under the IBM Common Public License.
> Best regards,
> -mb
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org