[JBoss JIRA] (TOOLSDOC-452) Generate Release Notes doc for JBDS 8.0.0Beta1
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-452?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-452:
-------------------------------------
Original Estimate: 6 hours
Remaining Estimate: 6 hours
> Generate Release Notes doc for JBDS 8.0.0Beta1
> ----------------------------------------------
>
> Key: TOOLSDOC-452
> URL: https://issues.jboss.org/browse/TOOLSDOC-452
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> Doc sections:
> 1. Introduction to Red Hat JBoss Developer Studio
> 1.1. About Red Hat JBoss Developer Studio
> 1.2. Use Cases of JBoss Developer Studio
> 2. About this Release
> 3. New Features
> 4. Resolved Issues
> 5. Known Issues
> 6. Apply this Release
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TOOLSDOC-453) Generate Release Notes doc for JBDS 8.0.0Beta2
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-453:
----------------------------------------
Summary: Generate Release Notes doc for JBDS 8.0.0Beta2
Key: TOOLSDOC-453
URL: https://issues.jboss.org/browse/TOOLSDOC-453
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Release Notes
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.2.0
Doc sections:
1. Introduction to Red Hat JBoss Developer Studio
1.1. About Red Hat JBoss Developer Studio
1.2. Use Cases of JBoss Developer Studio
2. About this Release
3. New Features
4. Resolved Issues
5. Known Issues
6. Apply this Release
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TOOLSDOC-451) Update explicit Kepler text and figs references in docs for 8.0 (Luna)
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-451:
----------------------------------------
Summary: Update explicit Kepler text and figs references in docs for 8.0 (Luna)
Key: TOOLSDOC-451
URL: https://issues.jboss.org/browse/TOOLSDOC-451
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.2.0
_Text_
*Installation Guide*
* 2.2 Supported Operating Systems and Architectures
* 3.3 Install JBoss Developer Studio BYOE
* 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
* 5.3 Upgrade from JBoss Developer Studio 7.0
* 6.3 Uninstall JBoss Developer Studio BYOE
*Getting Started Guide*
--
*Migration Guide*
* 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
* 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)* 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
*User Guide*
--
_Figs_
*Installation Guide*
* Fig 3.6 Ininstall JBoss Developer Studio BYOE via Eclipse Marketplace
* Fig 3.7 Confirm Selected Features Window
* Fig 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
* Fig 6.3 Confirm Selected Features Window
*Getting Started Guide*
--
*Migration Guide*
--
*User Guide*
--
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2745:
---------------------------------------
Docs Q: What is the outcome of this jira? Are we implementing the second method [~maxandersen] outlined - a check box for "Include Experimental" and the associated behind the scenes necessities?
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16386) Quick fix which offers to disable Facelet HTML Validator
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16386?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16386:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Quick fix which offers to disable Facelet HTML Validator
> --------------------------------------------------------
>
> Key: JBIDE-16386
> URL: https://issues.jboss.org/browse/JBIDE-16386
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsf
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> Facelet HTML Validator causes many false errors and we disabled it for projects with KB nature. Lets make a quick fix which offers to disable Facelet HTML Validator for any project.
> Actually we already have such a quick fix - DisableFaceletHTMLValidatorMarkerResolution
> we just need to make it visible for all kind of problems with validator_id - org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16363) improve the whatsnew section
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16363?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16363:
------------------------------------
In speaking with Max today re: https://github.com/jbosstools/jbosstools-website/pull/21, it seems one goal is to move these many whatsnew/*/*.html pages around & merge them so that we replace pages like :
http://jbosstools.github.io/jbosstools-website/whatsnew/arquillian/arquil...
http://jbosstools.github.io/jbosstools-website/whatsnew/browsersim/browse...
http://jbosstools.github.io/jbosstools-website/whatsnew/jst/jst-news-4.1....
with
http://jbosstools.github.io/jbosstools-website/whatsnew/4.1.1.Alpha1.html...
http://jbosstools.github.io/jbosstools-website/whatsnew/4.1.1.Alpha1.html...
http://jbosstools.github.io/jbosstools-website/whatsnew/4.1.1.Alpha1.html...
---
I'd also like to see CRx content relabelled to Final.
What about having some way to force-relabel all the CRx-latest pages to Final? That is, if the rendering engine sees "CR1" and no "CR2" it displays "Final" instead of "CR1"; if it sees CR2, it leaves CR1 as is and instead renames CR2 -> Final ?
> improve the whatsnew section
> ----------------------------
>
> Key: JBIDE-16363
> URL: https://issues.jboss.org/browse/JBIDE-16363
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.0.x
>
>
> the link to JBT versions should open a new page, not just expand the menu. They could link to the first component in the list of N&N.
> The N&N for a given version (.Alphax, .BetaX, .CRx) could be a single page using Bootstrap scrollspy to track scrolling a provide anchors (ie, URLs) that the users could share.
> For the .Final version, a merge of all N&N per component could be interesting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16363) improve the whatsnew section
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16363?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16363:
-------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.0.x)
> improve the whatsnew section
> ----------------------------
>
> Key: JBIDE-16363
> URL: https://issues.jboss.org/browse/JBIDE-16363
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha2
>
>
> the link to JBT versions should open a new page, not just expand the menu. They could link to the first component in the list of N&N.
> The N&N for a given version (.Alphax, .BetaX, .CRx) could be a single page using Bootstrap scrollspy to track scrolling a provide anchors (ie, URLs) that the users could share.
> For the .Final version, a merge of all N&N per component could be interesting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-12355:
-------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.0.x)
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha2
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://xcoulon.github.io/jbosstools-website/ <-- current version
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16389) Query parameters are not allowed in the runtime configuration for CordovaSim
by Vineet Reynolds (JIRA)
Vineet Reynolds created JBIDE-16389:
---------------------------------------
Summary: Query parameters are not allowed in the runtime configuration for CordovaSim
Key: JBIDE-16389
URL: https://issues.jboss.org/browse/JBIDE-16389
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.1.Final
Reporter: Vineet Reynolds
Related to JBIDE-16388, I'm creating a page: {{mobileapp.html}} that employs a query parameter ({{?target=cordova}}) to trigger the condition relevant to hybrid applications. The Hybrid Mobile application uses the REST APIs hosted on OpenShift via absolute URLs instead of relative URLs. The logic makes use of the presence/absence of the query parameter to use absolute (cloud) URLs instead of relative URLs.
When I create a runtime configuration to bypass JBIDE-16388 (to specify {{mobileapp.html}} as the start page), I cannot specify '?' in the path : http://www.screencast.com/t/ZYVMPtUWjq2
This fails only in CordovaSim, and the app works when run in emulators/devices.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months