David Sean Taylor <[EMAIL PROTECTED]> writes:
>> Yes. If you're using the tools, you simply change the class names for
>> the
>> tools in TR.props and then you're set.
>>
>And for the DynamicURI class?
The whole URI code has been reworked (newly written) and has now a
unified API. It resides in
On Tuesday, September 2, 2003, at 08:43 AM, Henning P. Schmiedehausen
wrote:
Deprecated DynamicURI and TemplateLink?
Yes.
Is there a migration path?
Yes. If you're using the tools, you simply change the class names for
the
tools in TR.props and then you're set.
And for the DynamicURI class?
I
David Sean Taylor <[EMAIL PROTECTED]> writes:
>> -The parameter parse has been heavily rewritten and back-ported from
>> Fulcrum, which was much better, and should give better results now
>>
>Thats a little scary without good HttpUnit/JWebUnit are similar tests
>in place
>I hope that the behavio
> Deprecated DynamicURI and TemplateLink?
> Is there a migration path?
> Im afraid we are heavily dependent on that one.
> My vote is that we do not move to the new version of Turbine until it
> is THOROUGHLY TESTED
Big +1 on that. I'd go further than that and defer this item until AFTER the
final
On Tuesday, September 2, 2003, at 12:51 AM, Henning P. Schmiedehausen
wrote:
David Sean Taylor <[EMAIL PROTECTED]> writes:
Your "problems" zones are basically the hotspots where we worked on
Turbine. :-)
- FileUpload now uses commons-fileupload
Yes I use this now in another project, it works g
David Sean Taylor <[EMAIL PROTECTED]> writes:
Your "problems" zones are basically the hotspots where we worked on
Turbine. :-)
- FileUpload now uses commons-fileupload
-The parameter parse has been heavily rewritten and back-ported from
Fulcrum, which was much better, and should give better re
On Monday, September 1, 2003, at 08:24 AM, Henning P. Schmiedehausen
wrote:
"Mark Orciuch" <[EMAIL PROTECTED]> writes:
Actually, we have just completed the move to commons logging. Is
logging the
only potential issue with Turbine?
I will try to release the 2.3 code base either today or
tomorro
"Mark Orciuch" <[EMAIL PROTECTED]> writes:
>Actually, we have just completed the move to commons logging. Is logging the
>only potential issue with Turbine?
I will try to release the 2.3 code base either today or
tomorrow. After this I intend to do some work in porting Jetspeed v1
to Turbine 2.3.
List
Konu: Re: moving to 2.3
ok, i patched my local copy to avoid usage of deprecated stuff .. but i
can't create a patch (seems to be a bug in eclipse 3.0 M3 :-(( )
martin
Mark Orciuch wrote:
>Martin,
>
>Let's direct further discussions on this topic here:
>
&g
2825
Best regards,
Mark Orciuch - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
-Original Message-
From: Martin Poeschl [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 3:35 PM
To: Jetspeed Users List
Subject: Re: moving to 2.3
ther
rom: Martin Poeschl [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 29, 2003 3:35 PM
> To: Jetspeed Users List
> Subject: Re: moving to 2.3
>
>
> ther should be no deprecation warnings using turbine-2.2 as most of the
> stuff has been removed .. i can send the patches for torque an
PROTECTED]
Sent: Friday, August 29, 2003 2:25 PM
To: Jetspeed Users List
Subject: Re: moving to 2.3
i can help with the migration .. moving to torque 3.1 is easy (just
replace the jars :-)
turbine is little bit harder as jetspped uses the turbine logging
services which has been removed .. so fixing
oeschl [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 29, 2003 2:25 PM
> To: Jetspeed Users List
> Subject: Re: moving to 2.3
>
>
> i can help with the migration .. moving to torque 3.1 is easy (just
> replace the jars :-)
> turbine is little bit harder as jetspped uses the tu
i can help with the migration .. moving to torque 3.1 is easy (just
replace the jars :-)
turbine is little bit harder as jetspped uses the turbine logging
services which has been removed .. so fixing the logging stuff first is
a good idea ;-)
martin
Ender Hikmet KILIÇOÐLU wrote:
Hi
any plan t
Hi
any plan to migrate next release of turbine for jetspeed v1
Ender
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
15 matches
Mail list logo