[EMAIL PROTECTED] escribió:
> Now that we have released a new 1.3a1 release that should hopefully
> dramatically cut down the installation issues of Jetspeed, it's time
> to really start working on Jetspeed 1.3a2 and what features we should
> include into this release.
>
> My personal target feature list for 1.3a2 is this :
>
> - fully catch up with Turbine
> * upgrade to the latest TDK Turbine
> * rework the TurbineUser dependent code to be only User dependent
> * start using ACLs
> * allow any Turbine templated system for layouts and screens with
> Velocity as default
Agree about that one. I prefer Velocity over jsp. I think we should also support
a pure XML template based solution, maybe using cocoon. I am implementing this
approach, together with Juan Carlos and Roberto. We will check in code for that
soon.
People using xalan 1.2.2 are seeing problems with our code. Maybe we should also
upgrade xalan.
>
> - rework the layout system
> * integrate templates in the other Jetspeed elements
> * rethink the PSML support
> * use the new Portlet API
With regards to the remaining multithreading issues, I think I will open a branch
where I can refactor and checkin the layout code to make sure that I can get it,
without disturbing other developments. In this process, some API can be changed,
and we can discuss alternatives easily if we have a working code base and we can
see the impact of the different alternatives. Anybody oposing?
>
> - redesign the customizer
> * be layout aware
> * use some portlet-customization entry points in order to provide
> portlet level customization.
+1 on that. I would like to recover also a portlet search and portlet browser. I
miss them a lot!
>
> - integrate the new Profiler
+1 again. I am testing it. I noticed that it is not used in the Info screen.
>
> - clean up the DiskCache
I will use the branch I said to check this code also. It is about ready for
testing now. There are changes in some places, and I prefer to have a stable code
base to test. I had lo loose a lot of time just catching up with code changes in
other places during december.
>
> - change the current Castor based persistence to something extensible
0 on that. I don't understand it very well.
>
>
> Comments or other features requests are welcome. I'll commit in the
> CVS a TODO-RELEASE-1.3a2 file just like we've done for 1.3a1. It's too
> early right now to target a release date but I definitely want it before
> ApacheCon.
I think we should have a release by then, with a cleaner layout system and better
documented code. Also the cache system should use the refactored version I'm
finishing.
>
>
> [As you may have noticed, I've been quite busy doing real work and didn't find
> a lot of time for working on Jetspeed. I should be able to contribute more
> to the project starting from next week...]
>
I have also been very occuppied. Now I am more focused, and I want to integrate
my changes soon, to avoid the nightmare of tracking changing code bases.
>
> --
> Raphaël Luta - [EMAIL PROTECTED]
> Vivendi Universal Networks - Services Manager / Paris
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/[email protected]/>
> List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
