Note that the only time that a version number will have a "M" at the end
of it is when there are changes in the local copy.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attac
OK, I went ahead and changed the system to instead spawn the
"svnrevision" command. It should gracefully set the version to
"unknown" if the "svnrevision" command can't be found.
On Sep 29, 2006, at 2:44 PM, Patrick Linskey wrote:
I would expect that we could get this info from running a
> >> 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 examp
> >> It looks like the revision number that we're getting in
> >> openjpa-lib/pom.xml is the latest revision number of the repo as a
> >> whole, not the latest revision number of just the openjpa
> trunk. Does
> >> anyone have a clue about how to get the latest revision for just
> >> openjpa?
>
>
It looks like the revision number that we're getting in
openjpa-lib/pom.xml is the latest revision number of the repo as a
whole, not the latest revision number of just the openjpa trunk. Does
anyone have a clue about how to get the latest revision for just
openjpa?
I had thought that would be
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.
I tried changing the goal to both 'package' and 'compile', but was
Hi,
It looks like the revision number that we're getting in
openjpa-lib/pom.xml is the latest revision number of the repo as a
whole, not the latest revision number of just the openjpa trunk. Does
anyone have a clue about how to get the latest revision for just
openjpa?
I would expect that we cou
Hi,
Currently, the openjpa-.zip that gets built in the
openjpa-project module contains all the individual module jars *and* the
openjpa-all-.jar. Is this desirable / necessary? My feeling is
that the dist should contain just openjpa-all-.jar, possibly
renamed to openjpa-.jar.
Thoughts?
-Patrick
