[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 commented on JBIDE-12355:
------------------------------------
[~xcoulon]: Here's a PR with newer Gemfile.lock contents:
https://github.com/jbosstools/jbosstools-website/pull/35
> 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.Beta1
>
> 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://tools-stg.jboss.org/ <-- current staged 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, 1 month
[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-16440:
---------------------------------------
I switched my local git repositories to jbosstools-4.1.x branch and test it - in tool tip and in popup window (by Ctrl+1) our quick fixes (Configure Problem Severity and Create JSF 2 composite component) are shown.
Trying to download and check JBDS 7.1.1 ...
> Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors
> ---------------------------------------------------------------------
>
> Key: JBIDE-16440
> URL: https://issues.jboss.org/browse/JBIDE-16440
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Final
> Reporter: Victor Rubezhny
> Assignee: Daniel Azarov
> Priority: Blocker
> Fix For: 4.1.2.CR1
>
> Attachments: JBossToolsHTMLEditor.png, WTPHTMLEditor.png
>
>
> It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes.
--
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, 1 month
[JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi... ]
Lukáš Fryč updated JBIDE-14964:
-------------------------------
Description:
When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally.
was:
When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be checked in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally.
> LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14964
> URL: https://issues.jboss.org/browse/JBIDE-14964
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Beta1
> Reporter: Lukáš Fryč
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.2.x
>
>
> When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
> In this mode, LiveReload does not work, because new resources are never published according to the IDE.
> However JRebel reloads those resources in a background.
> ----
> In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally.
--
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, 1 month