Hi everybody,
First of all, Happy 2006 for everyone :-)
Now, back to business, I'd like to discuss some issues regarding Cactus'
current status - in fact, I've been trying to send this message for
months, but just now I got the time to do so.
As there are so many thinks to say/discuss, let me try to break this
message in a couple of major topics:
1.Project status
The project seems quite dormant lately, mainly because Vincent is busy
with other projects (like Cargo and Maven 2). That's perfectly fine
(i.e., I'm not blaming him :-); in fact, he mentioned many times that he
doesn't even use Cactus anymore and the project needs a new leader. I
have faith this status is temporary, because there is a lot of stuff to
be done (see next topic) - I think the project just need a litthe push
to get going again. So, in order to recover that momentum, I'd like to
propose/ask 2 things:
First, one thing that might help push the project forward is moving it
to the new/proposed Testing TLP (Top Level Project). I mean, changes
always bring new energy (and curious people) to the project, so this
might be a good time for the move (besides, there's been some talk on
the Jakarta lists about moving most of the projects away from it).
Second, we need to identify who are the active committers and
contributors to the project. I know Vincent, Kasuhito, Kenney and myself
are committers and Yuan and Zheng were contributing some stuff - is
there anybody else?
2.Stuff to do
I can see at least 3 major developments that could be done for the
Cactus 1.8 (and/or 2.0) release(s):
- finish Cargo integration
- migrate build to Maven 2
- refactor package structure (relative to J2EE versions)
These features sounds like a lot of work, but we have already started
these activities; it's just a matter of coordinate the efforts to finish
them.
3.SVN status
Still regarding the Cargo integration, I think the SVN code is in a
delicated (read messy :-) situation. A few months ago, we decided to do
the Cargo integration in the HEAD and mantain a CACTUS_1_17 branch for
eventual releases before 1.18 (like 1.17.1 and 1.17.2). But I believe we
have also created another branch for Cargo integration. Long story
short, we need to unify those branches. My initial sugestion is to
revert the branches to the following status:
HEAD - revert to the old days where it had no Cargo integration. Right
now, it would be the equivalent of Cactus 1.17.1 + bugs fixed on
CACTUS_1_17 branch
CARGO_BRANCH (or whatever its named) - would contain the changes to
support Cargo, which would whatever the branch has now + Xuan's changes
to the HEAD + use of Cargo 0.7
other branches - do we have a branch for Maven 2 integration? And what
about the new packages hiearchy?
A second sugestion (if the first is to difficult to execute) is to leave
the branches as they are now (i.e., HEAD for Cargo Integration in Cactus
1.8 and BRANCH_1_17), but merging the changes done on the other Cargo
branch into the HEAD.
Whatever decision we make, I will 'volunteer' to do the job (as I was
the responbible for creating the branch in the first place :-).
Finally, notice that we haven't applied all of Xuan's patches yet...
4.Other issues
Besides the issues described in the previous sections, we still have
some minor stuff to fix/solve:
- Gump builds (A.K.A "The never ending story"): once we handle the Cargo
integration in the proper branch, we must either fix the Gump build or
remove Cactus from it. And when we (hopefully!) migrate Cactus to Maven
2, we could use Continuum to build it.
- site: we need to update the instructions on how to build Cactus from
SVN (and not CVS) anymore).
- HTMLUnit/HTTPUnit support: I believe there's been some threads
regarding Cactus' integration with these frameworks in the list, but
they have been dormant as well.
Regards,
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
