[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Nick Boldt edited comment on JBIDE-2720 at 11/26/13 5:01 PM:
-------------------------------------------------------------
You're still on Indigo?
We have newer versions of JBoss Tools and Red Hat JBoss Developer Studio for Juno (Eclipse 4.2.2) and Kepler (Eclipse 4.3.1), with new builds coming soon for Luna (Eclipse 4.4 M3) [1]. All new versions work with JBoss AS 4.2, as well as newer server runtimes [2].
[1] http://www.jboss.org/tools/download
[2] https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec...
Would it be possible for you to upgrade to something more recent?
The experimental version we have of Xulrunner for Windows 64-bit is only tested with Kepler (Eclipse 4.3 / JBoss Tools 4.1 / JBDS 7) at this time.
If you must stay on Indigo, and want to use the Visual Page Editor, your only option is to install the 32-bit version of JBoss Tools 3.3, with a 32-bit JDK.
was (Author: nickboldt):
You're still on Indigo?
We have newer versions of JBoss Tools and Red Hat JBoss Developer Studio for Juno (Eclipse 4.2.2) and Kepler (Eclipse 4.3.1), with new builds coming soon for Luna (Eclipse 4.4 M3).
http://www.jboss.org/tools/download
https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec...
Would it be possible for you to upgrade to something more recent?
The experimental version we have of Xulrunner for Windows 64-bit is only tested with Kepler (Eclipse 4.3 / JBoss Tools 4.1 / JBDS 7) at this time.
If you must stay on Indigo, and want to use the Visual Page Editor, your only option is to install the 32-bit version of JBoss Tools 3.3, with a 32-bit JDK.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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, 4 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Nick Boldt commented on JBIDE-2720:
-----------------------------------
You're still on Indigo?
We have newer versions of JBoss Tools and Red Hat JBoss Developer Studio for Juno (Eclipse 4.2.2) and Kepler (Eclipse 4.3.1), with new builds coming soon for Luna (Eclipse 4.4 M3).
http://www.jboss.org/tools/download
https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec...
Would it be possible for you to upgrade to something more recent?
The experimental version we have of Xulrunner for Windows 64-bit is only tested with Kepler (Eclipse 4.3 / JBoss Tools 4.1 / JBDS 7) at this time.
If you must stay on Indigo, and want to use the Visual Page Editor, your only option is to install the 32-bit version of JBoss Tools 3.3, with a 32-bit JDK.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-15622:
----------------------------------
Description:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png! !ReportBugStep3SourceView.png!
*Where to:*
1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
1. We should filter this dialog appearance (by Severity, by Existence, by Time), offer automatic send report?
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
was:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png!
*Where to:*
1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
1. We should filter this dialog appearance (by Severity, by Existence, by Time), offer automatic send report?
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png! !ReportBugStep3SourceView.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance (by Severity, by Existence, by Time), offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-16135:
------------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with javalement links to length() and CharSequence:
> !javadoc.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-16120) jsf.ui test failure
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16120?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-16120:
-----------------------------------------
Currently the test cannot work correctly because of Additional Info's are different in Java and XHTML Editors. As such, the test is hidden out from the suite, the new issue is opened for EL Content Assist in Java Editor's String values: JBIDE-16135, the test is to be corrected as part of that issue.
> jsf.ui test failure
> -------------------
>
> Key: JBIDE-16120
> URL: https://issues.jboss.org/browse/JBIDE-16120
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Alpha1
>
>
> {code}
> testCAForELJavaAndJSTCompare(org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest) Time elapsed: 3.391 sec <<< FAILURE!
> junit.framework.ComparisonFailure: Additional Info Strings must be equal expected:<<html><[head><style CHARSET="ISO-8859-1" TYPE="text/css">/* Font definitions */ html { font-family: 'Ubuntu',sans-serif; font-size: 11pt; font-style: normal; font-weight: normal; } body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size: 1em; } pre { font-family: monospace; } /* Margins */ body { overflow: auto; margin-top: 0px; margin-bottom: 0.5em; margin-left: 0.3em; margin-right: 0px; } h1 { margin-top: 0.3em; margin-bottom: 0.04em; } h2 { margin-top: 2em; margin-bottom: 0.25em; } h3 { margin-top: 1.7em; margin-bottom: 0.25em; } h4 { margin-top: 2em; margin-bottom: 0.3em; } h5 { margin-top: 0px; margin-bottom: 0px; } p { margin-top: 1em; margin-bottom: 1em; } pre { margin-left: 0.6em; } ul { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em;} li { margin-top: 0px; margin-bottom: 0px; } li p { margin-top: 0px; margin-bottom: 0px; } ol { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em; } dl { margin-top: 0px; margin-bottom: 1em; } dt { margin-top: 0px; margin-bottom: 0px; font-weight: bold; } dd { margin-top: 0px; margin-bottom: 0px; } /* Styles and colors */ a:link { color: #0000FF; } a:hover { color: #000080; } a:visited { text-decoration: underline; } a.header:link { text-decoration: none; color: #ffffff } a.header:visited { text-decoration: none; color: #ffffff } a.header:hover { text-decoration: underline; color: #000080; } h4 { font-style: italic; } strong { font-weight: bold; } em { font-style: italic; } var { font-style: italic; } th { font-weight: bold; } </style></head><body text="#ffffff" bgcolor="#000000"><h5><div style='word-wrap: break-word; position: relative; margin-left: 20px; padding-top: 2px; '><a href='eclipse-open:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo%7BUser.java%E2%98%83User'><!--[if lte IE 6]><![if gte IE 5.5]> <span alt='Open Declaration' style="border:none; position: absolute; width: 16px; height: 16px; left: -21px; filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='file:/home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.ui.test/target/work/data/.metadata/.plugins/org.eclipse.jdt.ui/jdt-images/1.png')"></span> <![endif]><![endif]--> <!--[if !IE]>--> <img alt='Open Declaration' style='border:none; position: absolute; width: 16px; height: 16px; left: -21px; ' src='file:/home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.ui.test/target/work/data/.metadata/.plugins/org.eclipse.jdt.ui/jdt-images/1.png'/> <!--<![endif]--> <!--[if gte IE 7]> <img alt='Open Declaration' style='border:none; position: absolute; width: 16px; height: 16px; left: -21px; ' src='file:/home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.ui.test/target/work/data/.metadata/.plugins/org.eclipse.jdt.ui/jdt-images/1.png'/> <![endif]--> </a><a class='header' href='eclipse-javadoc:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo'>demo</a>.<a class='header' href='eclipse-javadoc:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo%7BUser.java%E2%98%83User'>User</a></div>]</h5><br/>Created by...> but was:<<html><[body text="#ffffff" bgcolor="#000000"><h5><a class='header' href='eclipse-javadoc:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo'>demo</a>.User]</h5><br/>Created by...>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.TestCase.assertEquals(TestCase.java:261)
> at org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest.compareJavaAndJSTProposals(CAForELJavaAndJSTCompareTest.java:179)
> at org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest.testCAForELJavaAndJSTCompare(CAForELJavaAndJSTCompareTest.java:74)
> {code}
> {code}
> testELApplyMethodProposal(org.jboss.tools.jsf.jsp.ca.test.CAELApplyMethodProposalTest) Time elapsed: 3.772 sectestCAJsfAddInfoInELMessages(org.jboss.tools.jsf.jsp.ca.test.CAJsfAddInfoInELMessagesTest) Time elapsed: 1.989 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Additional Info exists but its value is not expected:
> Add. Info: [/* Font definitions */ html { font-family: 'Ubuntu',sans-serif; font-size: 11pt; font-style: normal; font-weight: normal; } body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size: 1em; } pre { font-family: monospace; } /* Margins */ body { overflow: auto; margin-top: 0px; margin-bottom: 0.5em; margin-left: 0.3em; margin-right: 0px; } h1 { margin-top: 0.3em; margin-bottom: 0.04em; } h2 { margin-top: 2em; margin-bottom: 0.25em; } h3 { margin-top: 1.7em; margin-bottom: 0.25em; } h4 { margin-top: 2em; margin-bottom: 0.3em; } h5 { margin-top: 0px; margin-bottom: 0px; } p { margin-top: 1em; margin-bottom: 1em; } pre { margin-left: 0.6em; } ul { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em;} li { margin-top: 0px; margin-bottom: 0px; } li p { margin-top: 0px; margin-bottom: 0px; } ol { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em; } dl { margin-top: 0px; margin-bottom: 1em; } dt { margin-top: 0px; margin-bottom: 0px; font-weight: bold; } dd { margin-top: 0px; margin-bottom: 0px; } /* Styles and colors */ a:link { color: #0000FF; } a:hover { color: #000080; } a:visited { text-decoration: underline; } a.header:link { text-decoration: none; color: #ffffff } a.header:visited { text-decoration: none; color: #ffffff } a.header:hover { text-decoration: underline; color: #000080; } h4 { font-style: italic; } strong { font-weight: bold; } em { font-style: italic; } var { font-style: italic; } th { font-weight: bold; } Base Name: resourcesResource Bundle: /JSF2KickStartWithoutLibs/JavaSource/resources.properties]
> Expected Value: [Base Name: resourcesResource Bundle: /JSF2KickStartWithoutLibs/JavaSource/resources.properties]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.jsf.jsp.ca.test.CAJsfAddInfoInELMessagesTest.testCAJsfAddInfoInELMessages(CAJsfAddInfoInELMessagesTest.java:62)
> {code}
--
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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-16135:
------------------------------------
Description:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
was:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor.
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
> Attachments: html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with javalement links to length() and CharSequence:
> !javadoc.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-16135:
------------------------------------
Description:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
was:
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
> Attachments: html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with javalement links to length() and CharSequence:
> !javadoc.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-16135:
------------------------------------
Description:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor.
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
was:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
> Attachments: html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor.
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with javalement links to length() and CharSequence:
> !javadoc.png|thumbnail!
--
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, 4 months