[
https://issues.apache.org/jira/browse/AXIS2C-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe updated AXIS2C-564:
-------------------------------------
Affects Version/s: 1.0.0
> Issues in the Axis2-C Installation Guide - Installing and Running on
> Microsoft Windows (win32)
> ----------------------------------------------------------------------------------------------
>
> Key: AXIS2C-564
> URL: https://issues.apache.org/jira/browse/AXIS2C-564
> Project: Axis2-C
> Issue Type: Bug
> Components: documentation
> Affects Versions: 1.0.0
> Environment: Windows XP
> Reporter: Evanthika Amarasiri
> Assigned To: Dushshantha Chandradasa
>
> The following issues were found in the "Installation Guide" under the heading
> "Installing and Running on Microsoft Windows (win32)"
> =======================================================================================================
> 1. In the Axis2-C Installation Guide, under the heading "2. Installing and
> Running on Microsoft Windows (win32)" it asks the user to download libxml but
> it does not say which version to download. When you go to the relevant site,
> you can see several versions of libxml. E.g. - LATEST_LIBXML2,
> LATEST_LIBXML2_IS_2.6.27, LATEST_LIBXSLT, LATEST_LIBXSLT_IS_1.1.20.
> Therefore, it should clearly state which version to download
> 2. In the Axis2-C Installation Guide under the heading "Using Binary Release"
> it says that you can download "Microsoft VSExpress2005" edition from the
> Microsoft Web site. It's better if you can give the site here. (It's true
> that you can google it and find out but it's good if you can specify the
> correct link to download Microsoft VSExpress2005. E.g.:- Specify the correct
> download page)
> 3. In the Axis2-C Installation Guide, no paths are specified as to where you
> can download the latest source and binary distributions. Appropriate links
> should be given in the relevant places
> E.g.:- Specify the axis2 download page -
> http://ws.apache.org/axis2/c/download.cgi
> 4. The path where the "configure.in" is located is not given (2. 2. Using The
> Source Release > 2.2.3. Editing configure.in File). When you search for the
> particular file, it gives 4 instances. Therefore, the document should clearly
> specify, which file the user should refer.
> 5. Under the heading "2.2.4. Compiling The Source" it asks the user to run
> the "vcvars32.bat" file but no such file exists in the source distribution
> (Assuming that it is in the source distribution). But the problem is I cannot
> find the "vcvars32.bat" file. Then I realised that this file resides in the
> VS installation folder. E.g.:- C:\Program Files\Microsoft Visual Studio
> 8\VC\bin. This is confusing to the user.
> The correct path of the "vcvars32.bat" have to be specified clearly.
> 6. The document states "build the system and create a directory named deploy
> under build directory:"
> What I understand by this is that you have to build the source first and then
> have to create a folder called deploy. What it should mean is that when you
> build the source, a folder named "deploy" will be created. Please rephrase
> this.
> 7. Under the heading "2. 2. Using The Source Release", first is asks the user
> to edit the "configure.in" file which is inside the source distribution and
> then as the next step it asks the user to extract the source distribution to
> a folder of choice, etc. How can you edit the file which is inside the source
> distribution without extracting it first? Therefore first it should ask the
> user to extract the source and then only it should ask the user to edit the
> particular file. Please rephrase.
> 8. Minor Issue - Under the heading "2.2.3. Editing configure.in File", it
> says that the default location for libxml2 is "C:\libxml2" but when you check
> the file you will see that the path specified in the file is
> "E:\libxml2-2.6.23.win32". This might be a bit confusing to the user.
> Therefore, the document should be replaced with the correct path.
> 9. Under the heading "2.2.3. Editing configure.in File" it should also state
> that the paths for iconv and zlib1 should also be replaced with the correct
> paths.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]