Please produce source releases.

[GoogleCodeExporter]

Currently when doing a release you bundle the source code but strip all
files that are used to compile/test your release.  Please in future release
your projects dev env with instructions on how to reproduce for release. 
My guess is that this would be a svn export, or equivalent, of the releases
tag.

As a member of the gentoo linux development team this means that I am
unable to version bump your software, and therefore only have a older
version jing-trang available to our users.

Please read
http://overlays.gentoo.org/proj/java/wiki/How_to_be_a_good_upstream for
more information on how to be a good upstream.

On a more personal note, and directed more towards a significant part the
java community,  There seem to be a large number of projects that 'believe'
( either explicitly or thru inaction ) that releases of the source are not
important.  All open source projects, in my opinion, should strive to
provide these releases.  Java projects have just the same
responsibilities/needs as a C/C++ in this regard.  The source, regardless
of language, should always be the primary 'release', everything else should
be only for convenience.  I consider this a fundamental step in the open
source software lifecycle.  I hope that you will also agree.

Original issue reported on code.google.com by alistair...@gmail.com on 22 Aug 2009 at 10:35

[GoogleCodeExporter]

All releases are tagged in the publicly accessible svn repository.  So the 
exact source used to build each release (along with tests and everything else 
needed to build) are available to everybody.  A lot of work went into ensuring 
it is really easy for anybody to build using from the repository.  Is there 
some reason you cannot get source by checking out a tag from a repository?

Original comment by jjc.jclark.com on 24 Aug 2010 at 4:35