Hi,
thanks very much at all for statements.
Greetings
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On Wed, Sep 15, 2010 at 11:57 AM, Gary Gregory
wrote:
>
> My preference would be for the sig "getVersion(Class)"
>
No objections here. That's just what we use. The getVersion() would
probably fit better with what we do everywhere else.
--
nt: Wednesday, September 15, 2010 03:55
To: Commons Developers List
Subject: Re: Version classes
On Wed, Sep 15, 2010 at 6:45 AM, sebb wrote:
>
> I like the idea.
>
> Apache JMeter does the same.
>
> It also includes the last SVN revision of whatever workspace was used
> to
On Wed, Sep 15, 2010 at 10:40 AM, Matt Benson wrote:
>
> Agreed--I didn't even realize this info was in Package. On the idea of
> manifest reading, though, I still have some code adapted from Ant's manifest
> code that does provide manifest access, if we want to polish it into a
> ManifestUtil
On Sep 15, 2010, at 8:04 AM, James Carman wrote:
> We should just add this to commons lang
Agreed--I didn't even realize this info was in Package. On the idea of
manifest reading, though, I still have some code adapted from Ant's manifest
code that does provide manifest access, if we want to
I personally agree with both Rahul and James. thanks.
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 15, 2010 at 3:04 PM, James Carman
wrote:
> We should just add this to commons lang
>
> On Sep 15, 2010 9:02 AM, "Rahul Akolkar" wrote:
>> On Wed, Sep 15, 2010
We should just add this to commons lang
On Sep 15, 2010 9:02 AM, "Rahul Akolkar" wrote:
> On Wed, Sep 15, 2010 at 8:57 AM, Torsten Curdt wrote:
>> IMO the thread showed that there are enough ways to get to that
>> information today.
>> I would not bother and call for the vote.
>>
>
>
> +1 to no
On Wed, Sep 15, 2010 at 8:57 AM, Torsten Curdt wrote:
> IMO the thread showed that there are enough ways to get to that
> information today.
> I would not bother and call for the vote.
>
+1 to not bothering for digester 2.1.
-Rahul
> On Wed, Sep 15, 2010 at 14:54, Simone Tripodi
> wrote:
>>
IMO the thread showed that there are enough ways to get to that
information today.
I would not bother and call for the vote.
On Wed, Sep 15, 2010 at 14:54, Simone Tripodi wrote:
> I'm going to call a vote for a new Digester release, shall this new
> stuff be included in the release?
> thanks in a
I'm going to call a vote for a new Digester release, shall this new
stuff be included in the release?
thanks in advance,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Wed, Sep 15, 2010 at 2:41 PM, Jochen Wiedmann
wrote:
>> James Carman wrote:
>
>> We use a method like
> James Carman wrote:
> We use a method like this:
>
> public static String versionOf(Class c) {
> final String version = c.getPackage().getImplementationVersion();
> return StringUtils.isEmpty(version) ? "n/a" : version;
> }
>
> So, if you want to know what version of Hibernate you're using,
James Carman wrote:
> On Wed, Sep 15, 2010 at 6:45 AM, sebb wrote:
>>
>> 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
>> pe
On Wed, Sep 15, 2010 at 8:01 AM, Jochen Wiedmann
wrote:
> Hmmm, doesn't provide access to the complete Manifest, but that's not
> what we need here. I'd opt to use that, rather than generated classes.
>
Right, for my particular case, all we cared about was the version from
the manifest. So, YAGN
On Wed, Sep 15, 2010 at 1:33 PM, James Carman
wrote:
> The Package class provides access to the manifest information.
Hmmm, doesn't provide access to the complete Manifest, but that's not
what we need here. I'd opt to use that, rather than generated classes.
Jochen
--
I Am What I Am And That'
On Wed, Sep 15, 2010 at 13:23, Jochen Wiedmann
wrote:
> On Wed, Sep 15, 2010 at 1:13 PM, James Carman
> wrote:
>
>> What do you mean reliable? Is it difficult to read a manifest?
>
> Can you tell me any about any non-trivial way to read it? Apart from
> URL manipulation and stuff like that? (Whi
On Wed, Sep 15, 2010 at 7:23 AM, Jochen Wiedmann
wrote:
> Can you tell me any about any non-trivial way to read it? Apart from
> URL manipulation and stuff like that? (Which is, IMO, unreliable,
> because it depends on certain assumptions on the URL.)
>
The Package class provides access to the ma
On Wed, Sep 15, 2010 at 1:13 PM, James Carman
wrote:
> What do you mean reliable? Is it difficult to read a manifest?
Can you tell me any about any non-trivial way to read it? Apart from
URL manipulation and stuff like that? (Which is, IMO, unreliable,
because it depends on certain assumptions
anifest. Hence version classes might be the only
> solution.
>
> Jochen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands,
I'd generally prefer the idea to read the manifest, in order to avoid
redundant information. However, I am unaware of any reliable manner of
reading the manifest. Hence version classes might be the only
solution.
Jochen
---
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
n 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
On Wed, Sep 15, 2010 at 6:45 AM, sebb wrote:
>
> 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 a
ct. 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.c
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 {
private Version() {
super();
}
private final static S
24 matches
Mail list logo
