I am not able to find Struts 1.2.0 in CVS. I cannot even find the tag
STRUTS_1_2_0. Can you please guide me?
Also, When I run the ant test.tomcat.all
I get the following compilation error
-------------------------------------------------------------------
/usr/local/struts/src/src/test/org/apache/struts/tiles/TestTilesPlugin.java:239:
cannot resolve symbol
[javac] symbol : method assertNotSame
(java.lang.String,org.apache.struts.tiles.DefinitionsFactory,org.apache.struts.tiles.DefinitionsFactory)
[javac] location: class org.apache.struts.tiles.TestTilesPlugin
[javac] assertNotSame("Factory from different modules",
factory1, factory2);
--------------------------------------------------------------------
I guess this method is available in junit framework. And I am sure it
has imported teh package correctly since I am not getting compilation
error message in methods assetEquals() and assertNotNull().
Any idea?
Abhishek
On Tue, 2004-05-18 at 13:49, Joe Germuska wrote:
> At 1:27 PM -0700 5/18/04, Abhishek Khandelwal wrote:
> >In that case, how are you differentiating between 1.2.0 and 1.2.1?
>
> Struts 1.2.0 is the code in CVS under the tag STRUTS_1_2_0
>
> >And if all, I need to get the CVS code, which days code should I take?
>
> Normally when you check code out of CVS, you get the newest of
> everything -- so it's not a specific day's code, it's NOW -- this is
> what's known as CVS HEAD, and technically, it's a moving target,
> although realistically, it hasn't been changing that quickly in the
> last couple of months.
>
> It is always possible using CVS to check out code to a specific date
> and time, or when tags have been applied, to a specific tag.
>
> If you use CVS to keep a current copy of the working code, then it's
> easy to keep up to date -- you can just do a CVS update and pick up
> any changes, bug fixes, or enhancements which have been made since
> your last checkout. Much easier than downloading a new source
> package, especially if you also make any local modifications to the
> code yourself -- Struts will deal with merging repository changes
> into your local copy.
>
> It just so happens that I just applied a patch to ExceptionHandler,
> so at this very instant, CVS is one bug "better" than the nightly
> source distribution (until the next one is made, of course.)
>
> Joe
>
>
> >Abhishek
> >
> >On Tue, 2004-05-18 at 13:09, Joe Germuska wrote:
> >> At 12:35 PM -0700 5/18/04, Abhishek Khandelwal wrote:
> >> >Thanks Joe for your detailed reply.
> >> >
> >> >Where can I get Struts 1.2.1 Version source code?
> >> >I am little skeptible of taking the todays nightly-build source code.
> >>
> >> There's no "release candidate" code for 1.2.1. Once
> >> commons-validator is released, we'll assess the open bugs, fix what
> >> we can and mark the others for "LATER", and then use that day's
> >> "nightly-build source code" to cut 1.2.1 -- so you can't do much
> >> better than CVS HEAD. (I never did understand the appeal of
> >> downloading source tarballs; it's much easier to keep up with changes
> >> using CVS...)
> >>
> >> >I have few more questions, like, does the 1.2.1 version support Tomcat
> >> >5.0. Since I am using Tomcat5. I can see from build-test.xml that it has
> >> >cactus test case for tomcat5.
> >> >
> >> >Also, if it supports tomcat5, would it be compatible to Servlet2.4?
> >> >
> >> >And lastly, would it be backward compatible, in terms of supporting
> >> >previous versions of tomcat?
> >>
> >> Regarding Servlet versions, Struts is built to work against Servlet
> >> 2.2/JSP 1.1. One of the outstanding bugs refers to some issues with
> >> differences between the HttpServletRequest interface, (as implemented
> >> in MultipartRequestWrapper) which has sprouted new methods in 2.3 and
> >> again in 2.4. But if you aren't using any of those things, then it
> >> should work fine in Tomcat 5 -- several people who post to this list
> >> or the [EMAIL PROTECTED] list refer to running Struts under Tomcat 5,
> >> although I have no personal experience.
> >>
> >> Open source code is yours -- especially if you're building from
> >> source -- so just grab what's in CVS HEAD and if you find bugs, fix
> >> 'em! (Or at least report 'em.) This is how we make it better.
> >>
> >> Joe
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
