From hadoop-dev-return-4074-apmail-lucene-hadoop-dev-archive=lucene.apache.org@lucene.apache.org Mon Oct 02 20:14:34 2006 Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 62007 invoked from network); 2 Oct 2006 20:14:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Oct 2006 20:14:34 -0000 Received: (qmail 64266 invoked by uid 500); 2 Oct 2006 20:14:33 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 64242 invoked by uid 500); 2 Oct 2006 20:14:33 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 64233 invoked by uid 99); 2 Oct 2006 20:14:33 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2006 13:14:33 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from [209.237.227.198] ([209.237.227.198:34898] helo=brutus.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id A8/17-24395-62371254 for ; Mon, 02 Oct 2006 13:14:30 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BEA0F71430D for ; Mon, 2 Oct 2006 13:14:20 -0700 (PDT) Message-ID: <9507280.1159820060778.JavaMail.root@brutus> Date: Mon, 2 Oct 2006 13:14:20 -0700 (PDT) From: "Doug Cutting (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-567) The build script should record the Hadoop version into the build In-Reply-To: <28945636.1159772659594.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/HADOOP-567?page=comments#action_12439303 ] Doug Cutting commented on HADOOP-567: ------------------------------------- The point about the Package stuff, is that, without much complexity (Ant adds a manifest to the jar), we can use a standard API for this, and some folks might benefit from that. We could include the same information (author, revision, etc.) but we'd encode it in the available fields, e.g., implementationVersion could be version+revision, vendor could be "Apache Software Foundation, built by ", etc. Someday someone might reasonably suggest that the Hadoop jar should include a manifest containing its version. (That's what happened with Lucene.) Should we then have two mechanisms to stamp builds with the version? It might sound like I feel strongly about this. I don't. Your approach has clear advantages over a Package-based solution: the values are more structured & can thus more easily be formatted as we wish. I just wanted to raise the Package issue for consideration. It's likely to arise again someday, so if we decide against it we should do so knowingly and have a rationale ready. (Like Serializeable, RMI, & other wheels we reinvent.) I'm also in general not very sympathetic to designing things for alternate build environments. We have a single supported build environment, Ant. If folks build things in other ways then it might not work. Doesn't Eclipse use the Ant build? Do we really need to support folks who've not configured their Eclipse environment to do so? (Note that storing the version in the jar manifest also mostly avoids this issue.) I feel slightly stronger about this one. > The build script should record the Hadoop version into the build > ---------------------------------------------------------------- > > Key: HADOOP-567 > URL: http://issues.apache.org/jira/browse/HADOOP-567 > Project: Hadoop > Issue Type: New Feature > Components: util > Affects Versions: 0.6.2 > Reporter: Owen O'Malley > Assigned To: Owen O'Malley > Fix For: 0.7.0 > > Attachments: version.patch > > > It would be good to compile the Hadoop version, subversion revision, and compilation date into the hadoop.jar file. > The web/ui would display the version for each of the server home page. > I'd also add "bin/hadoop version" to print the version information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira