Emmanuel,
You did a great job yesterday but you gotta deploy your changes to the
remote repos. You know that every time you make a significant API
change you should push jars up to the remote repository.
Yeah I know I did not mention this to many people. I'm trying to get
into the habit myself.
When API changes are made we have to deploy those changes to the
SNAPSHOT repository. Otherwise compilation issues make it so others
cannot point fix the code. Like Trustin tried to fix the server-ssl
problem by checking out server-ssl and could not build it without a full
rebuild because the shared-ldap changes broke everything and maven could
not pull down up to date snapshots.
NOW FOR THE FUNNY PART :D
*Alex does not want to admin this*
You could not really do this because I fudged up the deploy the last
time. My last deploy changed the permissions to exclude write access to
the group. Doh! So even if you followed the rules my last deployment
would not have allowed anyone else to update the repo.
So to do this right for the future we all might want to take a look at
the following confluence page Trustin has over here:
http://mina.apache.org/developer-guide.html
It shows how to deploy to the repo when changes are made to APIs.
Regards,
Alex
begin:vcard
fn:Alex Karasulu
n:Karasulu;Alex
org:Apache Software Foundation;Apache Directory
adr:;;1005 N. Marsh Wind Way;Ponte Vedra ;FL;32082;USA
email;internet:[EMAIL PROTECTED]
title:Member, V.P.
tel;work:(904) 791-2766
tel;fax:(904) 808-4789
tel;home:(904) 808-4789
tel;cell:(904) 315-4901
note;quoted-printable:AIM: alexokarasulu=0D=0A=
MSN: [EMAIL PROTECTED]
Yahoo!: alexkarasulu=0D=0A=
IRC: aok=0D=0A=
PGP ID: 1024D/4E1370F8 BBCC E8D8 8756 2D51 C3D4 014A 3662 F96F 4E13 70F8=0D=0A=
x-mozilla-html:FALSE
url:http://people.apache.org/~akarasulu
version:2.1
end:vcard
