On Wednesday, 26 June 2013, Barrie Treloar wrote: > On 26 June 2013 18:44, sebb <seb...@gmail.com <javascript:;>> wrote: > > Howewer the ASF releases source. > > If you don't provide a download link to the source how are users > > supposed to find it? > > > > I agree that most people are not going to want to download the original > source. > > But that does not mean it should be left unlinked. > > We provide all that for Maven core - the bit the users care about and run. > > Plugins are download by Maven. > Few, if any, user is going to download a source distribution of a > plugin and built it themselves. > If they are going to do that, then they are likely to want to work on > Jira issues or provide a patch and it makes much more sense to work > with source control. > And we have prominent links to the source control repositories, > including the tags.
I do not think it would be a major harm to add a reporting plugin to generate the dist download link for source bundles... As it can only add... I agree that there is no *requirement* for us to provide the download link... But there are things we can improve. Until recently, it was not clear to us that the source bundles had to be copied into the dist directory... Someone at infra wrote an audit script and we copied all the missing bundles over for plugins (they were on repository.apache.org so it is not that we hadn't generated them) I think we should turn on rat for all plugins, not just core... I will look into this next week if nobody else has... Most likely I will turn on rat without strong enforcement just yet, and then turn on zero tollerance in a month or so to give people the chance to fix rat issues and get out any emergency releases that might be required (eg if there is a CVE requiring a plugin release, you don't want that blocked while we review the integration test data that may or may not require an ASF license header for the test to be valid, and I'd rather have a valid set of exclusions rather than a "lets just get the build passing to make this release" approach which can get forgotten to unwind after) > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: dev-h...@maven.apache.org <javascript:;> > > -- Sent from my phone
