SNAPSHOTS can be modified (overridden by a new version of the snapshot or deleted) and will break the following release policy rule:
'Every ASF release MUST contain one or more source packages, which MUST be sufficient for a user to build and test the release provided they have access to the appropriate platform and tools.' If you are maintaining your own SNAPSHOT of a given project (e.g. commons-csv) and assuming they are not going to perform a release, you might be better performing a release yourself (Any23) which is not perfect but I have seen other projects doing it (e.g. https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.spark-project.hive%22 ) Having said that, I would really try to discuss with commons-csv if they could help and accept your changes and perform a release. [1] http://www.apache.org/legal/release-policy.html#source-packages On Thu, Feb 8, 2018 at 10:26 AM, lewis john mcgibbney <lewi...@apache.org> wrote: > Hi Folks, > Over at Any23 [0], we have, for some time, been depending upon an old > SNAPSHOT of commons-csv which we host in SVN [1] and utilize in our POM > [2]. > During a recent review process for our 2.2 release candidate, it was > pointed out that there may be an issue with this practice. > Can someone please point me towards documentation on this practice such > that we can determine if we need to fix the issue or if we can release the > candidate then fix for the next release? > Thank you kindly, > Lewis > > [0] http://any23.apache.org > [1] https://svn.apache.org/repos/asf/any23/repo-ext/ > [2] https://github.com/apache/any23/blob/master/pom.xml#L603-L606 > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc > -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
