You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Stephen McConnell <mc...@apache.org> on 2004/10/02 16:17:42 UTC
RE: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
All of the Excalibur projects are declared in a Gump definition which is
available to all Apache committers in the gump cvs module. The file in
question 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 the
build. It seems that the gump builder for maven may be generating
properties that are inconsistent with the Gump naming conventions. If
you get stuck in this area the best thing to do is to post the issues to
the general@gump.apache.org list.
Stephen.
> -----Original Message-----
> From: Leif Mortenson [mailto:leiflists@tanukisoftware.com]
> Sent: 02 October 2004 16:05
> To: Excalibur Developers List
> Subject: Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
>
> Sorry for my ignorance, but where are the gump projects configured?
The
> instrument jar/project names all changed when I restructured
Instrument
> a while back.
>
> excalibur-instrument-api -> excalibur-instrument-api
> excalibur-instrument-http -> excalibur-instrument-mgr-http
> excalibur-instrument-impl -> excalibur-instrument-mgr-impl
> excalibur-instrument-spi -> excalibur-instrument-mgr-api
> excalibur-instrument-altrmi -> X
>
> I'd take care of getting gump fixed as far as the instrument packages
if
> only
> I knew how....
>
> Cheers,
> Leif
>
> Gump Integration Build wrote:
>
> >To whom it may engage...
> >
> >This is an automated request, but not an unsolicited one. For
> >more information please visit http://gump.apache.org/nagged.html,
> >and/or contact folk at general@gump.apache.org.
> >
> >Project excalibur-instrument-spi has an issue affecting its community
> integration.
> >This issue affects 4 projects, and has been outstanding for 23L runs.
> >Project State : 'Failed'
> >The following are affected:
> > - excalibur-instrument-http : Repository of reusable components.
> > - excalibur-instrument-impl : Repository of reusable components.
> > - excalibur-instrument-manager : Repository of reusable
components.
> > - excalibur-instrument-spi : Repository of reusable components.
> >
> >
> >Full details are available at:
> >
> >
http://brutus.apache.org/gump/public/excalibur/excalibur-instrument-
> spi/index.html
> >
> >That said, some snippets follow:
> >
> >
> >The following annotations were provided:
> > -DEBUG- Sole output [excalibur-instrument-spi-02102004.jar]
identifier
> set to project name
> > -DEBUG- Dependency on junit exists, no need to add for property
> junit.jar.
> > -DEBUG- Dependency on checkstyle exists, no need to add for property
> checkstyle.jar.
> > -INFO- Made directory
>
[/usr/local/gump/public/workspace/excalibur/containerkit/instrument/mgr-
> api/target/classes]
> > -INFO- Failed with reason build failed
> > -INFO- Failed to extract fallback artifacts from Gump Repository
> >
> >
> >The following work was performed:
> >http://brutus.apache.org/gump/public/excalibur/excalibur-instrument-
> spi/gump_work/build_excalibur_excalibur-instrument-spi.html
> >Work Name: build_excalibur_excalibur-instrument-spi (Type: Build)
> >State: Failed
> >Elapsed:
> >Command Line: java -Djava.awt.headless=true -
> Xbootclasspath/p:/usr/local/gump/public/workspace/xml-
>
xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-
> xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-
>
xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xm
l-
> commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -
> Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -
> Dbuild.sysclasspath=only -
> Djunit.jar=/usr/local/gump/public/workspace/dist/junit/junit.jar -
> Dsrc.exclude.pattern=**/package.html -
>
Dcheckstyle.jar=/usr/local/gump/public/workspace/checkstyle/target/dist/
ch
> eckstyle-02102004/checkstyle-02102004.jar -Dproject.version=02102004
-f
> gump-build.xml jar
> >[Working Directory:
> /usr/local/gump/public/workspace/excalibur/instrument-manager/spi]
> >CLASSPATH :
>
/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/
ex
> calibur/containerkit/instrument/mgr-
>
api/target/classes:/usr/local/gump/public/workspace/excalibur/containerk
it
> /instrument/mgr-api/target/test-
> classes:/usr/local/gump/public/workspace/avalon-
>
trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-ap
i-
> 02102004.jar:/usr/local/gump/public/workspace/avalon-
> tools/tools/magic/target/deliverables/jars/avalon-tools-magic-
>
02102004.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/
lo
> cal/gump/public/workspace/ant/dist/lib/ant-
> stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
> launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-
>
nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/lo
ca
>
l/gump/public/workspace/excalibur/containerkit/instrument/api/target/exc
al
> ibur-instrument-api-1.2-
>
dev.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checksty
le
> -02102004/checkstyle-02102004.jar:/usr/local/gump/packages/antlr-
> 2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-
> regexp/build/jakarta-regexp-
> 02102004.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-
>
launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:
/u
> sr/local/gump/public/workspace/jakarta-
> bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-
> commons/beanutils/dist/commons-beanutils-
> core.jar:/usr/local/gump/public/workspace/jakarta-
> commons/cli/target/commons-cli-
> 02102004.jar:/usr/local/gump/public/workspace/jakarta-
> commons/collections/build/commons-collections-
> 02102004.jar:/usr/local/gump/public/workspace/jakarta-
> commons/logging/dist/commons-
> logging.jar:/usr/local/gump/public/workspace/jakarta-
> commons/logging/dist/commons-logging-
>
api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/
gu
> mp/public/workspace/jakarta-velocity/bin/velocity-
> 02102004.jar:/usr/local/gump/public/workspace/avalon-
>
trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-02102004.jar
--
> -------------------------------------------
> >Buildfile: gump-build.xml does not exist!
> >Build failed
> >---------------------------------------------
> >
> >
> >
> >
> >To subscribe to this information via syndicated feeds:
> > RSS: http://brutus.apache.org/gump/public/excalibur/excalibur-
> instrument-spi/rss.xml
> > Atom: http://brutus.apache.org/gump/public/excalibur/excalibur-
> instrument-spi/atom.xml
> >
> >
> >--
> >Gump E-mail Identifier (within run) #23.
> >Produced by Gump 2.1.0-alpha-0003.
> >[Run (40000002102004, brutus:brutus-public:40000002102004)]
> >http://brutus.apache.org/gump/public/index.html
> >http://brutus.apache.org/gump/public/options.html
> >
> >--
> >Apache Gump
> >http://gump.apache.org/ [Instance: brutus]
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> >For additional commands, e-mail: dev-help@excalibur.apache.org
> >Apache Excalibur Project -- URL: http://excalibur.apache.org/
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> For additional commands, e-mail: dev-help@excalibur.apache.org
> Apache Excalibur Project -- URL: http://excalibur.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Stephen McConnell wrote:
>Yep - that and the fact that maven is generating a version file as
>opposed to a date-stamped file (and every working maven example I could
>find had a hard coded version).
>
>Steve.
>
>
Ok, then I will go ahead and remove the component.version property
declaration when
calling maven as it does not appear to have any effect.
Change:
<maven basedir="deprecated/component" goal="jar">
<property name="component.version" value="@@DATE@@"/>
</maven>
To:
<maven basedir="deprecated/component" goal="jar"/>
I also went through and added hardcoded version numbers for all target jars.
Now to wait for the next Gump run...
Cheers,
Leif
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/
RE: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Stephen McConnell <mc...@apache.org>.
> -----Original Message-----
> From: Leif Mortenson [mailto:leiflists@tanukisoftware.com]
> Sent: 06 October 2004 04:52
> To: Excalibur Developers List
> Subject: Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
>
> Going on to look at the current maven output of
> "excalibur-instrument-mgr-impl", I see that it
> is saying that it can not find the following dependencies:
>
> excalibur-instrument-api-1.2-dev.jar
> excalibur-instrument-mgr-api-1.2-dev.jar
> xml-apis-2.0.2.jar
>
> Even if I get the excalibur-instrument-api project to correctly build
the
> excalibur-instrument-api-@@DATE@@.jar product, I believe this will
still
> lead
> to problems in dependent projects because they use the maven
project.xml
> file
> to decide on the required jar file names rather than the jar
> dependencies defined
> in the gump file.
>
> Is this the reason why you have been hard coding the versions into the
> gump file?
Yep - that and the fact that maven is generating a version file as
opposed to a date-stamped file (and every working maven example I could
find had a hard coded version).
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/
Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Going on to look at the current maven output of
"excalibur-instrument-mgr-impl", I see that it
is saying that it can not find the following dependencies:
excalibur-instrument-api-1.2-dev.jar
excalibur-instrument-mgr-api-1.2-dev.jar
xml-apis-2.0.2.jar
Even if I get the excalibur-instrument-api project to correctly build the
excalibur-instrument-api-@@DATE@@.jar product, I believe this will still
lead
to problems in dependent projects because they use the maven project.xml
file
to decide on the required jar file names rather than the jar
dependencies defined
in the gump file.
Is this the reason why you have been hard coding the versions into the
gump file?
Cheers,
Leif
Leif Mortenson wrote:
> Looking over the project/excalibur.xml file, I see that several other
> projects also use the
> @@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.
>>
>>
>>
>>> -----Original Message-----
>>> From: Leif Mortenson [mailto:leiflists@tanukisoftware.com]
>>> Sent: 05 October 2004 15:16
>>> To: Excalibur Developers List
>>> Subject: Re: [GUMP@brutus]: 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
>>>>>
>>>>
>> which
>>
>>
>>> is
>>>
>>>
>>>>> available to all Apache committers in the gump cvs module. The
>>>>>
>>>>
>> file in
>>
>>
>>>>> question 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
>>>>>
>>>>
>> the
>>
>>
>>>>> build. It seems that the gump builder for maven may be generating
>>>>> properties that are inconsistent with the Gump naming conventions.
>>>>>
>>>>
>> If
>>
>>
>>>>> you get stuck in this area the best thing to do is to post the
>>>>>
>>>>
>> issues
>>
>>
>>> to
>>>
>>>
>>>>> the general@gump.apache.org list.
>>>>>
>>>>> Stephen.
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>> ---------------------------------------------------------------------
>>
>>
>>>> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
>>>> For additional commands, e-mail: dev-help@excalibur.apache.org
>>>> Apache Excalibur Project -- URL: http://excalibur.apache.org/
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
>>> For additional commands, e-mail: dev-help@excalibur.apache.org
>>> Apache Excalibur Project -- URL: http://excalibur.apache.org/
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
>> For additional commands, e-mail: dev-help@excalibur.apache.org
>> Apache Excalibur Project -- URL: http://excalibur.apache.org/
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> For additional commands, e-mail: dev-help@excalibur.apache.org
> Apache Excalibur Project -- URL: http://excalibur.apache.org/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/
Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Looking over the project/excalibur.xml file, I see that several other
projects also use the
@@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.
>
>
>
>>-----Original Message-----
>>From: Leif Mortenson [mailto:leiflists@tanukisoftware.com]
>>Sent: 05 October 2004 15:16
>>To: Excalibur Developers List
>>Subject: Re: [GUMP@brutus]: 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
>>>>
>>>>
>which
>
>
>>is
>>
>>
>>>>available to all Apache committers in the gump cvs module. The
>>>>
>>>>
>file in
>
>
>>>>question 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
>>>>
>>>>
>the
>
>
>>>>build. It seems that the gump builder for maven may be generating
>>>>properties that are inconsistent with the Gump naming conventions.
>>>>
>>>>
>If
>
>
>>>>you get stuck in this area the best thing to do is to post the
>>>>
>>>>
>issues
>
>
>>to
>>
>>
>>>>the general@gump.apache.org list.
>>>>
>>>>Stephen.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>---------------------------------------------------------------------
>
>
>>>To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
>>>For additional commands, e-mail: dev-help@excalibur.apache.org
>>>Apache Excalibur Project -- URL: http://excalibur.apache.org/
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
>>For additional commands, e-mail: dev-help@excalibur.apache.org
>>Apache Excalibur Project -- URL: http://excalibur.apache.org/
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
>For additional commands, e-mail: dev-help@excalibur.apache.org
>Apache Excalibur Project -- URL: http://excalibur.apache.org/
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/
RE: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Stephen McConnell <mc...@apache.org>.
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.
> -----Original Message-----
> From: Leif Mortenson [mailto:leiflists@tanukisoftware.com]
> Sent: 05 October 2004 15:16
> To: Excalibur Developers List
> Subject: Re: [GUMP@brutus]: 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
which
> is
> >> available to all Apache committers in the gump cvs module. The
file in
> >> question 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
the
> >> build. It seems that the gump builder for maven may be generating
> >> properties that are inconsistent with the Gump naming conventions.
If
> >> you get stuck in this area the best thing to do is to post the
issues
> to
> >> the general@gump.apache.org list.
> >>
> >> Stephen.
> >>
> >>
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> > For additional commands, e-mail: dev-help@excalibur.apache.org
> > Apache Excalibur Project -- URL: http://excalibur.apache.org/
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> For additional commands, e-mail: dev-help@excalibur.apache.org
> Apache Excalibur Project -- URL: http://excalibur.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/
Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Leif Mortenson <le...@tanukisoftware.com>.
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 which is
>> available to all Apache committers in the gump cvs module. The file in
>> question 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 the
>> build. It seems that the gump builder for maven may be generating
>> properties that are inconsistent with the Gump naming conventions. If
>> you get stuck in this area the best thing to do is to post the issues to
>> the general@gump.apache.org list.
>>
>> Stephen.
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> For additional commands, e-mail: dev-help@excalibur.apache.org
> Apache Excalibur Project -- URL: http://excalibur.apache.org/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/
Re: [GUMP@brutus]: excalibur/excalibur-instrument-spi failed
Posted by Leif Mortenson <le...@tanukisoftware.com>.
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 which is
>available to all Apache committers in the gump cvs module. The file in
>question 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 the
>build. It seems that the gump builder for maven may be generating
>properties that are inconsistent with the Gump naming conventions. If
>you get stuck in this area the best thing to do is to post the issues to
>the general@gump.apache.org list.
>
>Stephen.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/