I'm all for starting maven2 first. Others have found the current Ant
system obtuse. It would be good to start fresh and clean.
We can kill two birds w/ one stone? Why not make the new server branch
an m2 branch. We keep the Avalon interfaces and, if we did it right, we
can drop the jar into a Phoenix container.
Regards,
Alan
Stefano Bagnara wrote:
The best place would be a james-server specific branch.
I would prefer if you start from the maven2 thing. Having branches
with different project structure from the trunk is not a good thing.
IMHO if we start pojo/xbean branch it would mean leave maven2 behind.
So, my idea is:
1) let's evaluate the maven2 port and vote on its adoption.
2) After the vote we can safely start refactorings in branches.
Stefano
Alan D. Cabrera wrote:
I insist that pojoification itself is "almost meaningless" and
utopistic: we should discuss on the real steps that each one would
include in a concrete roadmap.
If we intend to discuss this now, we should start a new thread ;-)
A new thread, agreed. But let me say this. A picture is worth a
thousand words and in our domain, that's code. I think that a
sandbox w/ some sample "conversions" would facilitate discussions.
I'm happy to host those samples in the xbean sandbox. I'm happy to
have them hosted else where. Thoughts?
---------------------------------------------------------------------
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]
