You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Tom Jordahl <to...@macromedia.com> on 2002/08/30 20:54:05 UTC
Build issues
Hi all,
A few things:
Did we every figure out why axis.properties is used for?
Is seems to be referenced in only 3 build files:
$ find . -type f -name "*.xml" -print | xargs fgrep axis.properties
./test/wsdl/interop3/emptysa.xml: <property file="axis.properties"/>
./test/wsdl/interop3/import1.xml: <property file="${basedir}/axis.properties"/>
./test/wsdl/interop3/RPCEncD.xml: <property file="axis.properties"/>
Is has some old stuff in it and I was going to update it, but if its just a leftover...
------------------------------------------------------------
Why do I get lots of these messages in the 'setenv' target when I build:
setenv:
[available] DEPRECATED - <available> used to override an existing property.
[available] Build file should not reuse the same property name for different values.
Can we remove the use of <available> since we require ant 1.5 to build?
------------------------------------------------------------
Why does this step *always* happen when I compile from the top level?
compile:
[echo] Compiling tools.ant
[echo] Building ForEach
[javac] Compiling 1 source file to D:\dev\xml-axis\java\build\tools
[echo] Building RunAxisFunctionalTest
[javac] Compiling 1 source file to D:\dev\xml-axis\java\build\tools
[echo] wsdl2java and java2wsdl
[javac] Compiling 2 source files to D:\dev\xml-axis\java\build\tools
[jar] Building jar: D:\dev\xml-axis\java\build\lib\axis-ant.jar
------------------------------------------------------------
--
Tom Jordahl
Macromedia Server Development
Re: Build issues
Posted by Matt Seibert <ms...@us.ibm.com>.
I can answer two of these for sure, but the axis.properties file is.... a
little weird:
The "deprecated" messages are an artifact of the componentization. Because
we want to ensure that properties are loaded at any level, I reload them at
the "leaf node" level. The new version of ANT (1.5.1 in the works right
now, according to Steve L.) will make these go away.
The tools.ant stuff is my new add. It happens everytime because I haven't
gotten the dependancy thing in place to exclude it's build. Because it is
minimal, I haven't put this on my priority list.... I will try to drop in
the fix for this today.
Matt Seibert mseibert@us.ibm.com
IBM External: (512) 838-3656 Internal: 678-3656
Hi all,
A few things:
Did we every figure out why axis.properties is used for?
Is seems to be referenced in only 3 build files:
$ find . -type f -name "*.xml" -print | xargs fgrep axis.properties
./test/wsdl/interop3/emptysa.xml: <property file="axis.properties"/>
./test/wsdl/interop3/import1.xml: <property file="${basedir}/axis.
properties"/>
./test/wsdl/interop3/RPCEncD.xml: <property file="axis.properties"/>
Is has some old stuff in it and I was going to update it, but if its just a
leftover...
------------------------------------------------------------
Why do I get lots of these messages in the 'setenv' target when I build:
setenv:
[available] DEPRECATED - <available> used to override an existing property.
[available] Build file should not reuse the same property name for
different values.
Can we remove the use of <available> since we require ant 1.5 to build?
------------------------------------------------------------
Why does this step *always* happen when I compile from the top level?
compile:
[echo] Compiling tools.ant
[echo] Building ForEach
[javac] Compiling 1 source file to D:\dev\xml-axis\java\build\tools
[echo] Building RunAxisFunctionalTest
[javac] Compiling 1 source file to D:\dev\xml-axis\java\build\tools
[echo] wsdl2java and java2wsdl
[javac] Compiling 2 source files to D:\dev\xml-axis\java\build\tools
[jar] Building jar: D:\dev\xml-axis\java\build\lib\axis-ant.jar
------------------------------------------------------------
--
Tom Jordahl
Macromedia Server Development