Sangjin Lee wrote:
The versions are definitely messy, and we need to sort it out.
How about calling the trunk the "2.0" version as it is based on mina 2.0.x
(easier to remember)? Let's keep the 1.0 version as is. But let's name it
"1.0-mina1".
The trunk will contain the 2.0 version. The name will remain trunk,
though. We will have to change the pom.xml to reflect this modification,
once the 1.0-mina1 branch will be created. (note that the mina1 suffix
is just used as a reminder)
As for subprojects,
the 1.0 client does not have separate common, client, and server
projects. That is only in the trunk pom.xml. And this actually goes
to the heart of this point. The common-client-server division is based on
the vision that both the client and server share a significant portion of
code.
As it stands right now,
the 1.0 branch has only the client portion, and there is no breakout
of the common piece. If possible, I'd like to keep it that way...
we can, but as the client depends on the current trunk, as soon as we do
some modifciation in trunk, the branch will be dead.
I suggest we go a bit further and copy all what we have in trunk in the
1.0 branch.
Now, we should create 3 sub projects in this branch, one for client
(what you want to work on), the server and commons. They will be
separated projects.
here is the structure I forsee :
/
branches
1.0-mina1
client
commons
server
pom.xml
NOTICE
README
tags
<nothing atm, but hopefully 1.0 soon>
trunk
client
commons
server
pom.xml
NOTICE
README
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
