Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.216.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=HmHJ6J8ZgCQCAp8smAzJaApbQxV0ezsZy165dRs5hkf+qByxExq1SEkqYCFQKZX39E
         CkmDpmI2PypPjNosEe+naSHUw5ddGKCLCy5mBWb8tdBsUUJRnuZF7gaulueeom1N4adC
         HmxixsoxRJF7zcXy3/p7p9P/M54OIUAZr7ypc=
MIME-Version: 1.0
In-Reply-To: <4C9083A6.3090609@healthcarion.de>
References: <4C9083A6.3090609@healthcarion.de>
Date: Wed, 15 Sep 2010 11:45:09 +0100
Message-ID: <AANLkTi=8SkEP74AsvGnYkHHp9D4HwtBfmoEsGXJKOrO-@mail.gmail.com>
Subject: Re: Version classes
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 15 September 2010 09:28, Michael Lieshoff
<michael.lieshoff@healthcarion.de> wrote:
> =A0Hi there,
>
> i have problems in big environments where different versions of Apache
> Commons projects exists, some older and others newer. I think in this cas=
e a
> version class is pretty, contains the version of the project. So a simple
> version request at runtime would be possible and it's not needed to read
> manifest informations. I searched about version classes in Apache Commons
> projects but i dont find anything.
>
> Here is a simple code fragment:
>
> package org.apache.commons.lang;
> public final class Version {
> =A0 =A0private Version() {
> =A0 =A0 =A0 =A0super();
> =A0 =A0}
> =A0 =A0private final static String VERSION =3D "2.4";
> =A0 =A0public static String getVersion() {
> =A0 =A0 =A0 =A0return VERSION;
> =A0 =A0}
> }
>
> What you think about it?

I like the idea.

Apache JMeter does the same.

It also includes the last SVN revision of whatever workspace was used
to build it.

Since the version is available to Maven (or Ant) it could update (or
perhaps create?) the version file as part of the build.

If we decide to include the SVN revision as well, we could also add
the SVN revision as a new manifest entry.

Which makes me wonder - maybe another way to do this would be to have
the getVersion() method read the Manifest entry?

> Best regards
>
> Michael.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org