openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: svn revision number
Date Fri, 29 Sep 2006 21:44:39 GMT
> >> I would expect that we could get this info from running and parsing
> >> 'svnversion -c', but it looks like we're digging into files  
> >> instead of
> >> running commands. Any insight into why this is?
> 
> Well, I had been loathe to spawn commands as part of the build  
> process. For example, what if someone is using Eclipse's built-in  
> Subversion client, and so do not have a separate "svnversion" 
> command  
> on their machine? Should we just fail the build, or silently ignore?
> 
> Parsing the .svn/entries file seemed like it would be a simpler  
> process. Unfortunately, there is another reason we may need 
> to change  
> this: the latest Subversion release (1.4) changes the format of this  
> file from XML to some custom format, which also breaks our parsing.  
> Bummer.

Personally, I think that our primary goal with this should be making
things work well in an automated environment, for uploading new build
artifacts to ibiblio / the website. 

> > Also, it would seem that the target runs during the 'run' goal  
> > (whatever
> > that is). The upshot is that 'mvn clean && mvn package' builds a jar
> > with no revision information, since 'run' seems to happen after jar
> > assembly is complete.
> 
> The goal is the action that you take on the plugin, not the phase in  
> which the action is performed. The "maven-antrun-plugin" only has a  
> single goal: "run".
> 
> > I tried changing the goal to both 'package' and 'compile', but was  
> > told
> > that that goal was unrecognized.
> 
> It is the "phase" element that needs to be changed. Try 
> "compile" and  
> see if that fixes it.

Yep, that did it. Thanks.

-Patrick
_______________________________________________________________________
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.

Mime
View raw message