On Thu, Jun 18, 2009 at 10:46 PM, Emmanuel Lecharny elecha...@apache.orgwrote:
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.
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 (
OK thanks. I'll first clean up the version numbers according to the
discussion we had so far.
Thanks,
Sangjin
On Fri, Jun 19, 2009 at 12:47 AM, Emmanuel Lecharny elecha...@apache.orgwrote:
Sangjin Lee wrote:
we can, but as the client depends on the current trunk, as soon as we do
some
Emmanuel Lecharny wrote:
Sangjin Lee wrote:
Thanks. I'll also check the trunk to see if changes are applicable
to the
trunk.
I'm not quite sure I understand what you mean by renaming it to
1.0-trunk.
The svn URL is .../mina/asyncweb/branches/1.0/... Do you mean to
rename it
to
Rick McGuire wrote:
Emmanuel Lecharny wrote:
Sangjin Lee wrote:
Thanks. I'll also check the trunk to see if changes are applicable
to the
trunk.
I'm not quite sure I understand what you mean by renaming it to
1.0-trunk.
The svn URL is .../mina/asyncweb/branches/1.0/... Do you mean to
Le Thu, 18 Jun 2009 13:47:20 +0200,
Emmanuel Lecharny elecha...@apache.org a écrit :
Rick McGuire wrote:
Emmanuel Lecharny wrote:
Sangjin Lee wrote:
Thanks. I'll also check the trunk to see if changes are
applicable to the
trunk.
I'm not quite sure I understand what you mean by
Julien Vermillard wrote:
Le Thu, 18 Jun 2009 13:47:20 +0200,
Emmanuel Lecharny elecha...@apache.org a écrit :
Rick McGuire wrote:
Emmanuel Lecharny wrote:
Sangjin Lee wrote:
Thanks. I'll also check the trunk to see if changes are
applicable to the
trunk.
I'm not
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.
As for subprojects,
the 1.0 client does not have separate common, client,
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
Hi,
We've been actively using the asyncweb client (the 1.0 version) in
production for a while, and I have a number of pent-up changes I wish to
contribute back. Our company also has a couple of critical enhancements in
mind, and I would like to see that done on this 1.0 branch.
I know that there
Sangjin Lee wrote:
Hi,
We've been actively using the asyncweb client (the 1.0 version) in
production for a while, and I have a number of pent-up changes I wish to
contribute back. Our company also has a couple of critical enhancements in
mind, and I would like to see that done on this 1.0
Thanks. I'll also check the trunk to see if changes are applicable to the
trunk.
I'm not quite sure I understand what you mean by renaming it to 1.0-trunk.
The svn URL is .../mina/asyncweb/branches/1.0/... Do you mean to rename it
to .../mina/asyncweb/trunk/1.0/...?
Also, please note that some
Sangjin Lee wrote:
Thanks. I'll also check the trunk to see if changes are applicable to the
trunk.
I'm not quite sure I understand what you mean by renaming it to 1.0-trunk.
The svn URL is .../mina/asyncweb/branches/1.0/... Do you mean to rename it
to .../mina/asyncweb/trunk/1.0/...?
+1... can't wait to see the contribution!
Jeff
On Jun 17, 2009, at 3:33 PM, Sangjin Lee wrote:
Hi,
We've been actively using the asyncweb client (the 1.0 version) in
production for a while, and I have a number of pent-up changes I
wish to
contribute back. Our company also has a couple of
14 matches
Mail list logo
