Bug 777836 (SOA-362) - SOA Getting Started Guide location
Summary: SOA Getting Started Guide location
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-362
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 CR1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CR2
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-24 00:31 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-06 07:24:06 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777841 0 medium CLOSED Multiple/different versions of ESB project README first file in RC1 build 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-362 0 None None None Never

Internal Links: 777841

Description Joshua Wulf 2008-01-24 00:31:55 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2008-01-24 02:48:12
project_key: SOA

The "SOA Installation and Getting Started Guide" [1] should go into the root of the docs directory. So it should look like this:

--docs
    |--- SOA_Getting_Started_Guide.pdf
    |---eap
    |---esb

http://engineering.redhat.com/docbot/en-US/JBoss_SOA_Platform/4.2/html/SOA_Getting_Started_Guide/
http://engineering.redhat.com/docbot/en-US/JBoss_SOA_Platform/4.2/pdf/SOA_Getting_Started_Guide/
Comment 1 Mark Little 2008-01-24 07:48:12 UTC 
Please remember to set the Component when creating issues.
Comment 2 Len DiMaggio 2008-01-25 17:17:41 UTC 
Link: Added: This issue related SOA-368
Comment 3 trev 2008-01-28 18:25:36 UTC 
will remove old getting started.pdf - will address as part of the whole docs restructure
Comment 4 Joshua Wulf 2008-02-06 07:24:06 UTC 
CR2 has the fix
Note You need to log in before you can comment on or make changes to this bug.