openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <>
Subject Re: Build data in built artifacts
Date Mon, 14 Aug 2006 21:19:56 GMT
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.

                 <replace file="target/classes/openejb-"
                 <replace file="target/classes/openejb-"
                 <replace file="target/classes/openejb-"

                 <!-- Add *.properties files -->
                 <copy todir="target/classes">
                   <fileset dir="src/main/java">
                     <include name="**/*.properties"/>

On Aug 14, 2006, at 2:00 PM, 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 into jars in a mvn environment?
> -Patrick
> -- 
> Patrick Linskey
> BEA Systems, Inc.
> ______________________________________________________________________ 
> _
> Notice:  This email message, together with any attachments, may  
> contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and   
> affiliated
> entities,  that may be confidential,  proprietary,  copyrighted   
> and/or
> legally privileged, and is intended solely for the use of the  
> individual
> or entity named in this message. If you are not the intended  
> recipient,
> and have received this message in error, please immediately return  
> this
> by email and then delete it.

View raw message