I don't think we can speak about "standard" practices, but Maven itself[1] publishes -src and -bin artifacts on the central repo.
+1 on NOT publishing them on central repo, but we should find an automated way to deploy them on SvnPubSub along the signature and checksums. best, -Simo [1] http://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.0.5/ http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Thu, Mar 28, 2013 at 3:00 PM, Emmanuel Bourg <ebo...@apache.org> wrote: > Hi, > > I just noticed that for the recent releases the source and binary > packages have been published in the Maven repository. I saw that with > fileupload 1.3 and daemon >= 1.0.11. > > Is this a "standard" practice? > > I find this very interesting because the sources.jar usually shipped is > great for browsing the code in our IDEs, but it can't really be used to > recompile the project (it doesn't provide the source of the generated > code for example). This is critical for downstream packagers like Debian > that insists in building everything from the source. The buildable > source distribution in Maven is likely to help them greatly. > > I would just note that we publish a src.zip and src.tar.gz artifact in > the Maven repository. We should probably publish only one to avoid > overloading the repository. > > Emmanuel Bourg > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
