Hi Martin, I ran 'mvn clean install' on a fresh checkout of the trunk and it built successfully first time. I didn't see any warnings.
My environment: Mac OSX 10.8.4, x86_64, Maven 3.03, JDK 1.7.0_21, time zone London UK. Ross On 28 Jun 2013, at 23:27, Martin Desruisseaux <[email protected]> wrote: > Hello all > > I finished porting the tests that I wanted. I think that the test coverage is > still insufficient, but we will hopefully start receiving feedbacks from > users. > > I would appreciate if some volunteers could try "mvn install" on their > machine. Some methods are locale or timezone sensitive. I tried to protect > the test cases against timezone changes, but I may have forgot some cases. > > I will try to read Suresh's instructions this weekend. Some tasks that popup > from my heads before to make a release are: > > * Update the web site and the wiki (the last "recent report" is 14 > months old) > * Re-organize the "getting started" instructions > * Review pending JIRA tasks > * Review javadoc > * Decide on the content of the distributed ZIP files. > > > I don't know yet if there is Apache recommendation about the content of the > distributed ZIP files. One proposal could be to provide 3 separated files: > binary, javadoc and source code. The content of the ZIP file for the binary > could be: > > README > LICENSE > NOTICE > bin/sis > bin/sis.bat > bin/sis.jar > etc/logging.properties > > > where "sis" and "sis.bat" would be convenience shell scripts (Unix and > Windows respectively) for invoking "sis.jar", and "etc" would be any > configuration file (only an optional "logging.properties" for now). > > Is there any though? > > Martin > > > Le 27/06/13 03:08, Suresh Marru a écrit : >> Hi Martin & Adam, >> >> No worries on this one, we all learn through the process and I learned the >> hard way. As Chris pointed out to earlier on this thread, one of the >> important aspect in ASF is getting the releases. We can informally roll-out >> RC's for testing. But before we can vote on a release, that has to be done >> on cryptographically signed artifacts. Also there are constraints on where >> the signed KEYS are located and so forth. Also, we need to properly follow >> the way we distribute release notes and also publish artifacts to nexus repo >> so downstream users can get them. >> >> I will be happy to help put together some detailed instructions on the >> website so we will have them for future. Here is a stating point on Airavata >> release management - >> http://airavata.apache.org/development/release-management.html >> >> Suresh >
