May 2014 - jbosstools-issues - Jboss List Archives

[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/2/14 4:08 AM: ------------------------------------------------------------- Looks like some formatting is correct and others ... not so much. Example: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (look for "+ __ Important") vs. https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (again, an embedded "Important" callout, but formatted more cleanly More problems: * image captions gone * procedures lose numbered steps --> becomes paragraphs (should be ordered list) * backticks = <command> * should we wrap bold around guibutton, guilabel, or make them all command tags? * can't render to pdf using pandoc or asciidoc :( * random "+" concat symbols to merge paras w/ images, which github renders as "+" instead of paragraph joiners * need more hard rules to separate sections (just top levels, with =) was (Author: nickboldt): Looks like some formatting is correct and others ... not so much. Example: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (look for "+ __ Important") vs. https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (again, an embedded "Importat" callout, but formatted more cleanly > 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 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17222) OpenShift wizard: Error dialog upon OpenShift server internal error after wizard completion

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-17222: ------------------------------------- Summary: OpenShift wizard: Error dialog upon OpenShift server internal error after wizard completion Key: JBIDE-17222 URL: https://issues.jboss.org/browse/JBIDE-17222 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.2.0.Beta1 Reporter: Marián Labuda There could be some dialog to warn user, that something goes wrong internally on server, when creating new application (after hitting the Finish button in New Application wizard). Currently, there is a Perl internal issue on OpenShift Enterprise (internal eng OpenShift instance). The error message is {code} com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domain/jbdstestdomain57/appli...: Unable to complete the requested operation due to: Permission denied - /var/www/openshift/broker/tmp/cache/9A6/BD0/carts_by_feature_perl-5.10. Reference ID: 2684a1f6b1e513ea44aa7661ff3d0a3e {code} but this message can be spotted only in eclipse log (also stacktrace). In IDE there is no support to get user know about issue. In better case, after click on the Finish button in OpenShift wizard nothing happen, in worse case there is a short time UI freeze. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17167: ------------------------------------- To verify, I had a "successful" build, no errors as far as I saw. Nice big letters told me BUILD SUCCESS or whatever. > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17167: ------------------------------------ That's seriously messed up. Why would rse.ssh.source be resolved but rse.ui.source not be? > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17112) Errors on importing GateIn Portal as Maven project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17112?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17112: -------------------------------- Fix Version/s: 4.2.0.Beta2 > Errors on importing GateIn Portal as Maven project > --------------------------------------------------- > > Key: JBIDE-17112 > URL: https://issues.jboss.org/browse/JBIDE-17112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, portal-gatein > Environment: - Fedora 20 > - OpenJDK 1.7.0_51 (latest from Fedora 20) > - JBoss Developer Studio 8.0.0.Beta1 (Beta1-v20140408-2350-B93) > Reporter: Juraci Paixão Kröhling > Fix For: 4.2.0.Beta2 > > Attachments: jbosstools-diagnostics-20140415084349.zip > > > When trying to import "GateIn Portal" as an "Existing Maven Project" in JBoss Developer Studio Beta with EAP, I see an error dialog with two messages: > - "JBoss Core Portlet 2.0 requires Java 1.5 or newer" > - "JBoss Core Portlet 2.0 requires Dynamic Web Module 2.5 or newer" > Steps to reproduce: > - Install JBoss Developer Studio with EAP > - Import "Existing Maven Project", selecting the root of the GateIn clone (ex: https://github.com/jpkrohling/gatein-portal) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17112) Errors on importing GateIn Portal as Maven project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17112?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-17112: ----------------------------------- Assignee: Fred Bricon > Errors on importing GateIn Portal as Maven project > --------------------------------------------------- > > Key: JBIDE-17112 > URL: https://issues.jboss.org/browse/JBIDE-17112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, portal-gatein > Environment: - Fedora 20 > - OpenJDK 1.7.0_51 (latest from Fedora 20) > - JBoss Developer Studio 8.0.0.Beta1 (Beta1-v20140408-2350-B93) > Reporter: Juraci Paixão Kröhling > Assignee: Fred Bricon > Fix For: 4.2.0.Beta2 > > Attachments: jbosstools-diagnostics-20140415084349.zip > > > When trying to import "GateIn Portal" as an "Existing Maven Project" in JBoss Developer Studio Beta with EAP, I see an error dialog with two messages: > - "JBoss Core Portlet 2.0 requires Java 1.5 or newer" > - "JBoss Core Portlet 2.0 requires Dynamic Web Module 2.5 or newer" > Steps to reproduce: > - Install JBoss Developer Studio with EAP > - Import "Existing Maven Project", selecting the root of the GateIn clone (ex: https://github.com/jpkrohling/gatein-portal) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16701) Arquillian not working with default maven settings from selecting the jboss-javaee6-webapp-archetype 7.1.3.Final

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16701?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16701: -------------------------------- Fix Version/s: 4.2.x > Arquillian not working with default maven settings from selecting the jboss-javaee6-webapp-archetype 7.1.3.Final > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16701 > URL: https://issues.jboss.org/browse/JBIDE-16701 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, maven > Affects Versions: 4.1.1.Final > Reporter: Dirk Gerrit Oort > Fix For: 4.2.x > > > (see https://community.jboss.org/message/860583#860583) > Create maven project with archetype selecting the jboss-javaee6-webapp-archetype 7.1.3.Final > use arq-jbossas-managed > use jboss 7.1.1 > run maven test > deployment is done but after deployment the test 'hangs' -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[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: ------------------------------------- Looks like some formatting is correct and others ... not so much. Example: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (look for "+ __ Important") vs. https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... (again, an embedded "Importat" callout, but formatted more cleanly > 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 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17209) only product for mylyn integration is JBossAS Server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17209?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-17209: ----------------------------------- Assignee: Alexey Kazakov Assigning to Alexey for investigation. If you need to do some modifications in Central then assign it back to me > only product for mylyn integration is JBossAS Server > ---------------------------------------------------- > > Key: JBIDE-17209 > URL: https://issues.jboss.org/browse/JBIDE-17209 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core, server > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Minor > > Using "report bug or enhancement" JBoss Tools shows up but then after that a list of "products" is shown and it just list JBossAS Server. > I would have expected Developer Studio too at least, and a few more key components. > Note: this might not be something base should add, but put it into central or jbds product makes sense I think. > -- Configuration Details -- > Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product) > Installed Features: > org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[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: ------------------------------------- OK, so a new approach... using shell script to batch-convert a whole folder of docbook .xml files into .adoc files (including images!): Before: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... After: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... More: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/d... Script: https://github.com/nickboldt/jbosstools-documentation/blob/TOOLSDOC-492/u... > 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 > > > 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2014