On Oct 22, 2015, at 4:00 PM, Thomas Weise <[email protected]> wrote:
> Hi Hitesh, > > Thanks for the review. > > 1) This seems to vary from project to project. I find examples that use a > dev directory on dist.apache.org, others copy the files into a user home > directory, others use Maven. I went with the latter because the > distribution to Maven is happening automatically when using the Apache > parent POM. The intention was to promote the files to dist.apache.org once > we have a successful vote as per > http://www.apache.org/dev/release-publishing.html#distribution > One of the reasons I called out not using maven is that when you finally promote the release, the jars will be published to the releases maven repo ( and not dist.apache ) and mirrored by maven central etc. This is not a place to host the source release tarball nor something to point the users to as a location for downloading a release. Likewise for not publishing the final assembly ( of jars ) to maven central Publishing to maven should be still done for the jars that you mean to provide as a convenience for downstream applications to consume but not for the source release tarball. thanks — Hitesh
