[ http://issues.apache.org/jira/browse/AXIS2C-376?page=all ]
Sanjaya Ratnaweera updated AXIS2C-376:
--------------------------------------
Fix Version/s: 1.0.0
(was: 0.96)
First 3 parts of this issue is relosved. The rest will be fixed in 1.0.
> --enable-tests and "make check" has multiple errors
> ---------------------------------------------------
>
> Key: AXIS2C-376
> URL: http://issues.apache.org/jira/browse/AXIS2C-376
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Unix/Linux)
> Affects Versions: 0.94
> Environment: Unix/Linux, maybe others
> Reporter: Chris Darroch
> Assigned To: Sanjaya Ratnaweera
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: axis2c-376.patch, axis2c-376.patch
>
>
> Normally, when using a package built with autoconf, one can expect to do:
> ./configure --enable-tests
> make check
> For Axis2/C this runs into a variety of problems. I noted a few of these
> issues
> in AXIS2C-313 as well, but this is a more detailed summary of the problems
> I've seen.
> Specifically:
> 1) The libcutest library is required, but it's a non-standard library, and
> isn't even installed as part
> of the CuTest package -- it has to be built by hand.
> 2) A number of the test programs have errors; for example, they free their
> env variable early and then segfault, or report a failure when none has
> occurred.
> 3) Test resource files are referenced that aren't supplied in the package,
> for example, Calculator.wsdl.
> 4) Some of the tests require that AXIS2C_HOME be set and that a valid
> axis2.xml file exist.
> 5) If --enable-tests is used for ./configure, then when "make install" runs
> in the test directories,
> it installs various programs and libraries in directories named itest,
> unit_test, and system_test
> under the specified --prefix. Even if these programs should be installed
> (which is arguable),
> they should be installed under the --bindir and --libdir locations, not
> --prefix.
> In my case, we try to make running "make check" a standard part of our global
> package
> installation framework, which is automated. I'll attach as files (if I can)
> the various patches
> we make to the Axis2/C test framework to deal with problems #2, #3, #4 and #5.
> To deal with problem #3 we also unpack the following resources, which I
> hunted around
> for on svn.apache.org:
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/XmlSchema/src/test/test-resources/
> into xml_schema
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/c/test/resources/wsdl/
> into woden/test
> To deal with problem #4, we patch samples/server/axis2.xml to not engage
> the addressing module, and then point AXIS2C_HOME to samples/server
> in our build directory before running "make check". That allows the tests to
> run
> without having already done a "make install" -- since our installation
> framework won't
> install the package until it's seen a successful "make check" run!
> Finally, to deal with problem #1, we build and install libcutest prior to
> building, testing,
> and installing Axis2/C, using the CuTest package and the trick found in this
> axis-c-dev mailing list posting:
> http://www.mail-archive.com/axis-c-dev@ws.apache.org/msg04697/Makefile
> In general, though, all these tricks shouldn't be necessary. A user should
> be able to
> download the axis2c package, run ./configure --enable-tests and "make check"
> with
> no special knowledge, I believe.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
