[JBoss JIRA] (JBDS-3259) Markdown Viewer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3259?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3259:
-----------------------------
Component/s: jsp/jsf/xml/html source editing
> Markdown Viewer
> ---------------
>
> Key: JBDS-3259
> URL: https://issues.jboss.org/browse/JBDS-3259
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Priority: Critical
> Fix For: 8.0.2.GA, 9.0.0.Alpha1
>
> Attachments: markdowneditor.gif
>
>
> Most of our quickstarts and example applications come with a Markdown readme.md that provides the end-user with key instructions on how to execute the example. In today's Eclipse/JBDS, this markdown file is normally displayed as pure source/text. Ideally, the file would render just as it does for github, including with "clickable links".
> The current poor "wrapping" is problematic for readability
> http://www.screencast.com/t/n4Zvwv0W
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3259) Markdown Viewer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3259?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3259:
-----------------------------
Fix Version/s: 8.0.2.GA
9.0.0.Alpha1
> Markdown Viewer
> ---------------
>
> Key: JBDS-3259
> URL: https://issues.jboss.org/browse/JBDS-3259
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Priority: Critical
> Fix For: 8.0.2.GA, 9.0.0.Alpha1
>
> Attachments: markdowneditor.gif
>
>
> Most of our quickstarts and example applications come with a Markdown readme.md that provides the end-user with key instructions on how to execute the example. In today's Eclipse/JBDS, this markdown file is normally displayed as pure source/text. Ideally, the file would render just as it does for github, including with "clickable links".
> The current poor "wrapping" is problematic for readability
> http://www.screencast.com/t/n4Zvwv0W
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3259) Markdown Viewer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3259?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3259:
----------------------------------
TL;DR... so we want to add the Mylyn Docs Wikitext feature to the JBDS/BYOE core feature so it's installed OOTB?
> Markdown Viewer
> ---------------
>
> Key: JBDS-3259
> URL: https://issues.jboss.org/browse/JBDS-3259
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification
> Reporter: Burr Sutter
> Priority: Critical
> Attachments: markdowneditor.gif
>
>
> Most of our quickstarts and example applications come with a Markdown readme.md that provides the end-user with key instructions on how to execute the example. In today's Eclipse/JBDS, this markdown file is normally displayed as pure source/text. Ideally, the file would render just as it does for github, including with "clickable links".
> The current poor "wrapping" is problematic for readability
> http://www.screencast.com/t/n4Zvwv0W
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3279:
-----------------------------
Fix Version/s: 9.0.x
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, maven
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.x
>
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months