I would have preferred if the mailet project was created by COPYING instead of MOVING from trunk so that trunk would have been fully working and functional during this transition.
Apart from this issue, that I hope will have a short life, thank you for taking care of this! I have a couple of requests: 1) Please give me the time to fix the m2 pom stuff before trying to call a release for mailet 2.3. 2) Maybe we should use 2.3.1 or 2.4 as the version number as the 2.3 release is the jar we bundled in the official james 2.3.0. On the other side it is true that the api has not changed since james 2.3.0 release, so it would only be a repackage of the same version (is there a best practice in ASF for this?) Stefano PS: weird choice to write this to private and mailet-api ;-) Danny Angus ha scritto: > Hi, > > I've created the sub-project structure for mailet in /james/mailet/trunk > > Noel has kindly moved the source from server/trunk mailet and > mailet-api into this. > (N.B. *not* james/transport/mailets) > > I still have to: > > 1/ create a snapshot jar to fix the broken server/trunk > 2/ generate the website > 3/ call a vote and cut a release of mailet 2.3 > 4/ get the commit mails directed to the mailet-api list > > > d.
