Hi Simon, I built it without running tests and got it working fine (with a minor but that I believe is fixed in the trunk now)
mvn -Dmaven.test.skip=true clean package or whatever target you choose. I have been running a fair amount of manual testing (ad hoc) and it seems to work fine for the simple scenarios (send, recv, dir,list cd). Wheather it is production safe ? You probably have to do your own testing depending on the usage you plan for. Best Curt ----Ursprungligt meddelande---- Från: [EMAIL PROTECTED] Datum: 28-03-2008 14:33 Till: <[email protected]> Ärende: RE: [ftpserver] how to build the ftpServer Maybe my intervention is related. I tried building the ftpserver project using maven 2.0.8 (mvn install) but unfortunately it fails, the unit tests fail. Did anyone had the same failure? It's pretty annoying. Also, how mature is the project? Can I start using this in a commercial application or is it still too unreliable? (From the unit tests, I would believe it is not ready yet...) I hope I will not offend anyone but, to avoid breaking the trunk build, I would recommend you to adopt a development branch that would synchronize with the trunk branch only if all unit tests pass. This way, the user won't check out stuff that is unreliable and break unit test. Simon -----Original Message----- From: Emmanuel Lecharny [mailto:[EMAIL PROTECTED] Sent: March-28-08 8:59 AM To: [email protected] Subject: Re: [ftpserver] how to build the ftpServer Mark Webb wrote: > While I agree that this is an option, none of the other MINA > subprojects require this. For consistency, they should all be the > same. > yes, but nothing is perfect at first :) > I am sorry if I am nitpicking and I apologize if I am upsetting > anyone, but as this program grows and evolves we should try to make > things easier for the users in order to gain more users and continued > satisfaction for the program. > +1. That means people provide some patches, helps, documentation too. As this is a collaborative effort, sharing info about what's wrong and how to fix it is the way to go. This will make users happy :) > Another question I have, the pom.xml requires that maven 2.0.5 or > 2.0.7 are used. OS X comes with 2.0.6 and this causes a problem. Is > there a reason why 2.0.6 cannot be used? > Well, I don't know, but 2.0.7 fixes some bugs in 2.0.6, so there is no reason we should stick with a buggy version when a new one is out there. May be looking on the Maven site for a release note could help ? -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org
