I don't have a strong opinion either way. If minor pom changes are needed to sign the release that can be documented. I'm not sure if that is acceptable for the Apache release procedures however.
In the staging repository, I do not see the -sources jars. Did you activate the 'dist' profile? -Scott On 3/1/11 11:39 AM, "Doug Cutting" <[email protected]> wrote: >With a minor change to lang/java/pom.xml I was able to stage this to the >following repository: > >https://repository.apache.org/content/repositories/orgapacheavro-084/ > >I couldn't get gpg:sign to create valid signatures without changing the >pom. > >Should I re-roll the rc tarball because of this change? > >Doug > >On 03/01/2011 09:53 AM, Doug Cutting wrote: >> I have created a second candidate build for Avro release 1.5.0. >> >> Changes are listed at: >> >> http://tinyurl.com/avro150 >> >> Please download, test, and vote by 4 March. >> >> http://people.apache.org/~cutting/avro-1.5.0-rc2/ >> >> Thanks, >> >> Doug
