Hi Mladen, Mladen Turk wrote:
> On 03/30/2013 11:59 PM, Gary Gregory wrote: >> On Mar 30, 2013, at 18:48, sebb <seb...@gmail.com> wrote: >> >>> On 30 March 2013 20:50, Mladen Turk <mt...@apache.org> wrote: >>> >>>> On 03/30/2013 09:06 PM, Jörg Schaible wrote: >>>> >>>> Jörg Schaible wrote: >>>>> >>>>>> >>>>>> the manifest of the commons-daemon-1.0.15.jar contains a strange >>>>>> entry: >>>>>> >>>>>> =========== %< ============= >>>>>> Implementation-Build: UNKNOWN_BRANCH@r??????; 2013-03-28 >>>>>> 13:53:43+0100 =========== %< ============= >>>>>> >>>>>> This contains normally the subversion number. Did you built the >>>>>> release from a checkout? It looks more like an export. >>>> Sure I did. As always (seems the same trash is in previous versions) >>>> I always build from export as the user would from .tar.gz >>> >>> It works OK if you build from a checkout (can be read-only). >>> >>> >>>> Not sure what would be the reason to have that (SVN) info in the >>>> manifest at the first place. >>> >>> It shows that the build was done from the relevant tag. >> >> I thought the Commons process was clear that building from the tag was >> the only way to go because it is the tag we vote on. >> > > This procedure must be fixed. There are vendors out there that > produce .jar files without using SVN, but rather our distribution > artefacts. Does it mean that our distribution artefacts are invalid !? No, but what we release into the Maven repository is unique. Even if some rebuilds the jars, the MD5/SHA1-hashes will be always different, simply because the manifest also includes build time, name of the current user, OS, ... - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
