> From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
> Behalf Of Marc Prud'hommeaux
> Sent: Wednesday, August 23, 2006 9:43 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Build data in built artifacts
>
>
> Interesting idea, although we'd need some w
Behalf Of Marc Prud'hommeaux
Sent: Tuesday, August 22, 2006 7:46 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Build data in built artifacts
I've gone ahead and committed something that does Bryan's
suggestion:
generates a /META-INF/revision.properties file and outputs t
nskey
BEA Systems, Inc.
> -Original Message-
> From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
> Behalf Of Marc Prud'hommeaux
> Sent: Tuesday, August 22, 2006 7:46 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Build data in built artifacts
>
I've gone ahead and committed something that does Bryan's suggestion:
generates a /META-INF/revision.properties file and outputs the
current Subversion revision number to it.
The org.apache.openjpa.conf.OpenJPAVersion class will load that file
and store it in the static "REVISION_NUMBER"
I dorked with it some more, and got it to the point where it wrote out a
properties file with the subversion revision info in it (a la David's
example)... but then ran into a wall in terms of getting the scope of
that property to hang around long enough to stuff it into. I hopped on
the #maven
On Aug 14, 2006, at 2:14 PM, Bryan Noll wrote:
I just have to play with it a bit in order to get a latest and
greatest rev number.
If you find a clean way to get the svn info let me know as I've
wanted that for OpenEJB and Geronimo for some time.
I've resorted to some pretty extreme lengt
Bryan-
FYI, I had played with this a little while ago ... I got the
subversion revision number using the maven-antrun-plugin and
xmlproperty task to parse the .svn/entries file, but I couldn't
figure out how to pass the value of the property from the ant plugin
to the global Maven propert
Here is the technique I use on OpenEJB. Note the version here is
hardcoded cause at the time ${pom.currentVersion} didn't work. They
may have fixed that since. Anyway, at runtime we just read this file
out of the classpath. Geronimo adopted the same technique.
org.apache.
Patrick...
Looks like the OpenJPA version number is already getting tossed in there as:
Implementation-Version: 0.9.0
We can stuff a subversion revision number in there by using
'maven-jar-plugin'... I just have to play with it a bit in order to get
a latest and greatest rev number.
Bryan N
Lemme take a crack at it...
Patrick Linskey wrote:
Hi,
I think it'd be nice if each of the modules could encode svn revision
number and OpenJPA version number information into the built jars,
presumably in a manifest entry. Does anyone have any knowledge about how
to coerce this type of info in
Hi,
I think it'd be nice if each of the modules could encode svn revision
number and OpenJPA version number information into the built jars,
presumably in a manifest entry. Does anyone have any knowledge about how
to coerce this type of info into jars in a mvn environment?
-Patrick
--
Patrick L
11 matches
Mail list logo