Sangjin Lee wrote:
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.
Where do you see the (1.0 branch) client dependency on the asyncweb trunk?
I'm looking at the pom.xml (
https://svn.apache.org/viewvc/mina/asyncweb/branches/1.0/client/pom.xml?revision=682452&content-type=text%2Fplain)
but I don't see a dependency on the asyncweb trunk (only mina 1.1.x and
other libraries). Maybe I'm being thick...
I was refering to trunk's client :
https://svn.apache.org/viewvc/mina/asyncweb/trunk/client/pom.xml?view=co
So in your case (1.0), this is not a problem. However, it may be
interesting to see the client as a separated project anyway.
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
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
