[JBoss JIRA] (JBDS-3023) Universal installer step4 Java statement needs updating
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-3023?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-3023:
----------------------------------
Priority: Blocker (was: Major)
> Universal installer step4 Java statement needs updating
> -------------------------------------------------------
>
> Key: JBDS-3023
> URL: https://issues.jboss.org/browse/JBDS-3023
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta1
> Reporter: Michelle Murray
> Priority: Blocker
>
> Universal installer, step 4 states:
> "JBoss Developer Studio works with Java 6 and 7 and has been tested with OpenJDK, Oracle and Apple JDK."
> According to the approved QE test plan (mojo DOC-932620):
> * Only Java 7 and Java 8 are supported for running the IDE (Java 6 support for app development only)
> * Apple JDK (which is Java 6) is not supported for running the IDE; it's supported for app development only
> For clarity, suggest changing text to:
> "JBoss Developer Studio can be run with Java 7 and 8 and has been tested with OpenJDK and Oracle JDK."
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16388) Cordovasim does not use the Hybrid Mobile project's start page
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16388?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-16388:
-------------------------------------
{quote}
Ilya Buziuk This is news to me. I thought CordovaSim already supported the content tag.
{quote}
I was wrong here. Actually we do have content tag support. I have tested it against Beta1 and everything works just fine. [~vineet.reynolds] could you try to reproduce the bug on Beta1?
> Cordovasim does not use the Hybrid Mobile project's start page
> --------------------------------------------------------------
>
> Key: JBIDE-16388
> URL: https://issues.jboss.org/browse/JBIDE-16388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Attachments: startPage.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When I run a Hybrid Mobile project under CordovaSim, it does not use the start page defined in {{config.xml}}.
> If the application were to use a different application start page, say {{mobileapp.html}} in {{config.xml}}, CordovaSim reports the following error: http://www.screencast.com/t/8odNCS5FWK
> I'm forced to create a new runtime configuration that explicitly defines the start page again. This is not necessary for running under the Android emulator or device, and is a problem only under CordovaSim.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16388) Cordovasim does not use the Hybrid Mobile project's start page
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16388?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-16388:
--------------------------------
Fix Version/s: (was: 4.2.x)
> Cordovasim does not use the Hybrid Mobile project's start page
> --------------------------------------------------------------
>
> Key: JBIDE-16388
> URL: https://issues.jboss.org/browse/JBIDE-16388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Attachments: startPage.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When I run a Hybrid Mobile project under CordovaSim, it does not use the start page defined in {{config.xml}}.
> If the application were to use a different application start page, say {{mobileapp.html}} in {{config.xml}}, CordovaSim reports the following error: http://www.screencast.com/t/8odNCS5FWK
> I'm forced to create a new runtime configuration that explicitly defines the start page again. This is not necessary for running under the Android emulator or device, and is a problem only under CordovaSim.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16931) Support for linked folders in cordovasim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16931?page=com.atlassian.jira.plugi... ]
Ilya Buziuk edited comment on JBIDE-16931 at 5/3/14 12:15 PM:
--------------------------------------------------------------
[~maxandersen], [~gercan] assuming that CS runs as a separate process the only idea that comes in my mind is:
1. Get all linked folders from the project
2. Pass parameter pairs of *linked folder name* and *actual location of the folder* for launching CS
3. Creating jetty handlers in a loop (number of handlers == number of linked folders)
- hosting all actual locations of the linked folders
- mapping linked folder name to location
Does it sound right?
was (Author: ibuziuk):
[~maxandersen], [~gercan] assuming that CS runs as a separate process the only idea that comes in my mind is:
1. Get all linked folders from the project
2. Pass parameter pairs of *linked folder name* and *actual location of the folder* for launching CS
3. Creating jetty handlers in a loop (number of handlers == number of linked folders)
- hosting all actual locations of the linked folders
- mapping linked folder name to location
Does it sounds right?
> Support for linked folders in cordovasim
> ----------------------------------------
>
> Key: JBIDE-16931
> URL: https://issues.jboss.org/browse/JBIDE-16931
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Alpha2
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Linked folders are not honored when project is run on CordovaSim
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16931) Support for linked folders in cordovasim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16931?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-16931:
-------------------------------------
[~maxandersen], [~gercan] assuming that CS runs as a separate process the only idea that comes in my mind is:
1. Get all linked folders from the project
2. Pass parameter pairs of *linked folder name* and *actual location of the folder* for launching CS
3. Creating jetty handlers in a loop (number of handlers == number of linked folders)
- hosting all actual locations of the linked folders
- mapping linked folder name to location
Does it sounds right?
> Support for linked folders in cordovasim
> ----------------------------------------
>
> Key: JBIDE-16931
> URL: https://issues.jboss.org/browse/JBIDE-16931
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Alpha2
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Linked folders are not honored when project is run on CordovaSim
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt edited comment on TOOLSDOC-492 at 5/3/14 10:51 AM:
--------------------------------------------------------------
After much ado, we can now generate from docbook all the following formats: pandoc extended markdown, asciidoc, pdf, epub, html5.
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... -> screenshot: [^openshift-chapter-generated-pdf.png]
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... -> screenshot: [^openshift-chapter-generated-epub.png]
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
The script now allows for commandline flags which will optionally produce the 3 extra formats (html, pdf, and epub), and can swap docbook tags markdown/asciidoc don't understand for tags they do.
Remaining TODOs will be tracked in the script, as they'll be fixed there too.
{code:title=https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/util/docbook2asciidoc.sh}
# TODO: fix remaining indented blocks; do we need to worry about indented CODE blocks, or is EVERYTHING just paragraphs?
# TODO: do we still want to add hard rules before each new top level "=" sections?
{code}
Note that TOC entries work (see especially in PDF and epub formats), and in HTML are simply the section title, lowercased, with dashes for spaces. For example, here's an anchor to the Connect To OpenShift section:
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
was (Author: nickboldt):
After much ado, we can now generate from docbook all the following formats: pandoc extended markdown, asciidoc, pdf, epub, html5.
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... -> screenshot: [^openshift-chapter-generated-pdf.png]
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... -> screenshot: [^openshift-chapter-generated-epub.png]
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
The script now allows for commandline flags which will optionally produce the 3 extra formats (html, pdf, and epub), and can swap docbook tags markdown/asciidoc don't understand for tags they do.
Remaining TODOs will be tracked in the script, as they'll be fixed there too.
{code:title=https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/util/docbook2asciidoc.sh}
# TODO: figure out what tags to use instead of <command> if we want *bold*, /italic/, or _underline_ instead of `code`
# TODO: this should use <tags> not just tagNames so that no copy gets changed (eg., command or procedure or step)
# TODO: fix remaining indented blocks; do we need to worry about indented CODE blocks, or is EVERYTHING just paragraphs?
# TODO: add hard rules before each new top level "=" sections
{code}
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-492:
-------------------------------------
After much ado, we can now generate from docbook all the following formats: pandoc extended markdown, asciidoc, pdf, epub, html5.
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
The script now allows for commandline flags which will optionally produce the 3 extra formats (html, pdf, and epub), and can swap docbook tags markdown/asciidoc don't understand for tags they do.
Remaining TODOs will be tracked in the script, as they'll be fixed there too.
{code:title=https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/util/docbook2asciidoc.sh}
# TODO: figure out what tags to use instead of <command> if we want *bold*, /italic/, or _underline_ instead of `code`
# TODO: this should use <tags> not just tagNames so that no copy gets changed (eg., command or procedure or step)
# TODO: fix remaining indented blocks; do we need to worry about indented CODE blocks, or is EVERYTHING just paragraphs?
# TODO: add hard rules before each new top level "=" sections
{code}
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt updated TOOLSDOC-492:
--------------------------------
Attachment: openshift-chapter-generated-epub.png
openshift-chapter-generated-pdf.png
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt edited comment on TOOLSDOC-492 at 5/3/14 9:53 AM:
-------------------------------------------------------------
After much ado, we can now generate from docbook all the following formats: pandoc extended markdown, asciidoc, pdf, epub, html5.
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... -> screenshot: [^openshift-chapter-generated-pdf.png]
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... -> screenshot: [^openshift-chapter-generated-epub.png]
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
The script now allows for commandline flags which will optionally produce the 3 extra formats (html, pdf, and epub), and can swap docbook tags markdown/asciidoc don't understand for tags they do.
Remaining TODOs will be tracked in the script, as they'll be fixed there too.
{code:title=https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/util/docbook2asciidoc.sh}
# TODO: figure out what tags to use instead of <command> if we want *bold*, /italic/, or _underline_ instead of `code`
# TODO: this should use <tags> not just tagNames so that no copy gets changed (eg., command or procedure or step)
# TODO: fix remaining indented blocks; do we need to worry about indented CODE blocks, or is EVERYTHING just paragraphs?
# TODO: add hard rules before each new top level "=" sections
{code}
was (Author: nickboldt):
After much ado, we can now generate from docbook all the following formats: pandoc extended markdown, asciidoc, pdf, epub, html5.
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d...
The script now allows for commandline flags which will optionally produce the 3 extra formats (html, pdf, and epub), and can swap docbook tags markdown/asciidoc don't understand for tags they do.
Remaining TODOs will be tracked in the script, as they'll be fixed there too.
{code:title=https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/util/docbook2asciidoc.sh}
# TODO: figure out what tags to use instead of <command> if we want *bold*, /italic/, or _underline_ instead of `code`
# TODO: this should use <tags> not just tagNames so that no copy gets changed (eg., command or procedure or step)
# TODO: fix remaining indented blocks; do we need to worry about indented CODE blocks, or is EVERYTHING just paragraphs?
# TODO: add hard rules before each new top level "=" sections
{code}
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months