On 15 February 2012 07:42, Roman Shaposhnik <r...@apache.org> wrote: > Hi! > > On Tue, Feb 14, 2012 at 11:31 PM, Jarek Jarcec Cecho <jar...@apache.org> > wrote: >> Hi Roman, >> we're definitely open to embrace any Apache policy for naming files. Can you >> point me to some written docs? > > AFAIK, it would be fair to say that Apache, in general, is all > about source releases. The binary artifacts are simply convenience > artifacts and thus it makes sense that the "default" tarballs are > source tarballs. > > I'm not sure I can quote chapter and verse, my experience comes from > doing Apache Bigtop > Project which is an integration point between at least a dozen > different Apache projects. > When I pulled your RC into Bigtop the other day it was the only > project that I had to modify > my scripts for. Everything else follows the most default naming convention.
There are certainly other naming conventions in common usage. AIUI, by default Maven appends -bin and -src to archives (not jars). However projects may drop the -bin and keep the -src (e.g. Commons) Also Tomcat (though that does not use Maven to build). Have a look at some of the other projects under the dist/ tree. There is a different naming convention for the jars which are intended for upload to Maven repositories. In that case, the binary jar cannot have a suffix; -source and -javadoc are used for the obvious purposes. > Hope this helps. > > Thanks, > Roman. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
