@@DATE@@ but from the Gump logs, they also seem to be having problem.
The way "excalibur-event-api" does it is to hard code the version into the gump file.
This seems like it would be very difficult to maintain, which is the purpose of using the
@@DATE@@ token.
It looks like there was an attempt to set the version when launching maven with the following
declaration.
<maven basedir="containerkit/instrument/api" goal="jar">
<property name="component.version" value="@@DATE@@"/>
</maven>
The problem is this does not seem to work. Playing around with running Maven, directly,
the only way that I could figure out to do this was to set the "maven.final.name" property.
This will most likely not set the version correctly in places like the jar manifests. From what
I could find, it looks like it would be necessary to set the following three properties:
<maven basedir="containerkit/instrument/api" goal="jar">
<property name="project.currentVersion" value="@@DATE@@"/>
<property name="pom.currentVersion" value="@@DATE@@"/>
<property name="maven.final.name" value="excalibur-instrument-api-@@DATE@@"/>
</maven>
It would be nice if there was a single property that could be set. :-/
I will give this a try for the next gump run and see how it works for the instrument api
project. If all goes well then I will go though and make these changes for the rest of the
excalibur projects.
Cheers, Leif
Stephen McConnell wrote:
The failure your currently getting is to do with the output declaration in the excalibur-instrumentation-api definition. Currently you have:
<jar name="target/excalibur-instrument-api-@@DATE@@.jar"/>
However, the maven build is generating an output:
target/excalibur-instrument-api-1.2-dev.jar
If you update the <jar> element to the following you should be ok.
<jar name="target/excalibur-instrument-api-1.2-dev.jar"/>
Stephen.
which-----Original Message----- From: Leif Mortenson [mailto:[EMAIL PROTECTED] Sent: 05 October 2004 15:16 To: Excalibur Developers List Subject: Re: [EMAIL PROTECTED]: excalibur/excalibur-instrument-spi failed
The changes I committed to CVS didn't appear to be used by this last gump run. Is there something else that I need to do?
Cheers, Leif
Leif Mortenson wrote:
Ok, I went through and updated the internal instrument project references. I guess we will see how successfully tonight when it run.
I added several alias projects so other projects referencing them would still work. Not sure what the policy is on changing other project's gump files. Probably not something that should be done.
Cheers, Leif
Stephen McConnell wrote:
All of the Excalibur projects are declared in a Gump definition
isfile in
available to all Apache committers in the gump cvs module. The
thequestion is:
/gump/project/excalibur.xml
Please note there this is a gump/maven issue that results in the
generation of inconsistent property files during the execution of
Ifbuild. It seems that the gump builder for maven may be generating
properties that are inconsistent with the Gump naming conventions.
issuesyou get stuck in this area the best thing to do is to post the
to---------------------------------------------------------------------
the [email protected] list.
Stephen.
---------------------------------------------------------------------To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
