Re: branches (was: Re: svn commit: r292559... )

[Kenney Westerhof <fo...@neonics.com>]

On Fri, 30 Sep 2005, Zhong ZHENG wrote:

Hi,
> Hi,
>
> I updated the wiki page for the maven 2 migration discussion:
> http://wiki.apache.org/jakarta-cactus/GeneralDiscussions/Maven2Migration

I just updated it and added some comments - sorry about the layout, I've
got zero experience in Wiki page editing.

> IMHO, maybe it will be better to keep the migration code in a separate
> branch and merge to head later when the migration is finished.

Ok. This is a bit more work later on (I'm not sure if merging moved
directories will work fine) but it's the safest for now.
I'll try to check wheter it's feasible to keep the branch up-to-date with
changes in trunk. That way we only need to 'switch' the trunk with the
branch when everybody agrees it is finished.

> Also, I am a newbie committer of the Pluto project, and am planning to add
> portlet support for Cactus. Do you think the current architecture of Cactus
> is flexible enough to add such support easily? I saw that you planned to
> refactory Cactus architecture and create version 2. So how about that effect
> now?

I'm not sure about the code architecture, but the project architecture
will be better suited in the maven2 case. I think it's best to add
support in a new subproject, since the current codebase runs fine without
that support. We can look at this like a new module or 'plugin' for
cactus. I expect you're going to have to change some existing classes
to enable support for portlets; if the projects are separated the
integration will be more dynamic and probably allows for easier
integration of future changes. Plus it'll help converting to maven2
later on.

-- Kenney

> Regards.
>
> On 9/30/05, Kenney Westerhof <fo...@neonics.com> wrote:
> >
> > On Fri, 30 Sep 2005, Zhong ZHENG wrote:
> >
> > Which branches are actually being updated? I'm used to working on trunk
> > for a next release, and when it's released create a tag + branch to
> > work on bugfixes for released versions.
> >
> > I'm going to have to change some code and move some code around in order
> > to have a better project structure, and merging will be difficult
> > afterwards. However, for now, I'm merely trying to get things working,
> > and get feedback about the new project structure. Is something final is
> > decided on, I can always start again.
> >
> > However, it might be best if the efforts to move to cargo (and other
> > current development) are all done in one branch. That would require
> > updating the ant build system to work with the new structure, but that's
> > no problem.
> >
> > Here are the options:
> >
> > - merge maven2 branch to head
> > - merge maven2 branch to another branch
> > - keep working in a separate branch, and start over/try to merge
> > later
> > - another option....
> >
> > WDYT?
> >
> > -- Kenney
> >
> >
> --
>
> ZHENG Zhong
>
> 1 Avenue Alphand
> 75116 Paris, France
> +33 6 76 80 45 90
>
> http://heavyz.sourceforge.net
> http://heavyz.blogspot.com
> http://spaces.msn.com/members/zhengzhong
>

--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org