[JBoss JIRA] (TOOLSDOC-289) Adhering to Red Hat and IBM writing styles
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-289?page=com.atlassian.jira.plug... ]
Vlado Pakan closed TOOLSDOC-289.
--------------------------------
Verified on https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0...
> Adhering to Red Hat and IBM writing styles
> ------------------------------------------
>
> Key: TOOLSDOC-289
> URL: https://issues.jboss.org/browse/TOOLSDOC-289
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide
> Affects Versions: 4.0.0.Beta1
> Reporter: Michelle Murray
> Assignee: Isaac Rooskov
> Fix For: 4.0.0.Final
>
>
> About: JBDS Getting Started Guide, 5.0.1
> Issue: The following do not adhere to the Red Hat or IBM writing styles
> [1.1,P2,L2] OS > operating system
> [Table1.1,R4,C2] Web pages > web pages
> [1.2,P3,L1] just > omit
> [3.1.1,P1,L1] you should follow > follow
> [3.1.1,B3,L1] Please > omit
> [3.1.1,B3,L2] you've > you have
> [3.1.1,Note,L3] i.e. > that is
> [3.2.2,B2] in a terminal window > on the command line
> [3.2.2] you launch JBoss > you start JBoss
> [4.2.1,Operating System] reports the Operating System > operating system
> [4.2.1,Linux distribution version] as the Operating System > operating system
> [5.1,After Fig5.6, P1, L1] go to Section > see Section
> [5.2,After Fig5.14,P1,L2] A screen will then appear > A window will then open
> [5.2,After Fig5.19,P1,L2] button that appears. > button in the window that opens.
> [7.1,After Fig7.3] should now appear > should now be visible
> [7.2,B1] right click > right-click the server's name
> [7.3,P1,L1] right click > right-click
> [7.3,P1,L1] press Stop. > select Stop.
> [9,P1,L1] you'll > you will
> [9,P2,L1] We'll assume that > It will be assumed that
> [9.1,P1,L1] i.e. > that is
> [9.1,P1,L2] Thus this section will perform you all necessary steps on how to do this. > omit?
> [9.1,After Fig9.1] should appear > should be visible
> [9.2,B1] Right click > Right-click
> [9.2.1,P1,L1] Let's now make a little change so that a JSP page displays “Hello World!” message. > To edit the JSP page so that it displays the “Hello World!” message, insert the following line inside the <body> </body> tags: ...
> [9.2.2,After Fig9.6,P1,L1] Let's add > To add ...:
> [9.2.3.1,After Fig9.7] Right click > Right-click
> [9.2.3.1,After Fig9.7] select New Archive -> JAR
> [9.2.4,B1] e.g. > For example, insert this piece of code
> [9.2.5,B2] right click > right-click
> [9.2.5,B2] haven't > have not
--
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
13 years, 1 month
[JBoss JIRA] (TOOLSDOC-287) Alternatives command needs a priority number to work
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-287?page=com.atlassian.jira.plug... ]
Vlado Pakan closed TOOLSDOC-287.
--------------------------------
Verified in https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0...
> Alternatives command needs a priority number to work
> ----------------------------------------------------
>
> Key: TOOLSDOC-287
> URL: https://issues.jboss.org/browse/TOOLSDOC-287
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide
> Affects Versions: 4.0.0.Beta1
> Environment: Fedora 17 x86_64
> Reporter: Michelle Murray
> Assignee: Isaac Rooskov
> Fix For: 4.0.0.Final
>
>
> About: JBDS Getting Started Guide 5.0.1. The second Note in 3.1.1 gives information about using the alternatives command to add JDK.
> Issue: These instructions did not work for me using alternatives version 1.3.59. I made the assumption that each sudo command should be input separately so perhaps this is where I went wrong. The use of the given commands, with jdk1.6.0_24 changed for update 37, resulted in the instructions for using the alternatives commands being output on the command line as below:
> {noformat}[mmurray@dhcp-0-244 ~]$ sudo /usr/sbin/alternatives --install "/usr/bin/java" "java" "/usr/java/jdk1.6.0_37/bin/java"
> alternatives version 1.3.59 - Copyright (C) 2001 Red Hat, Inc.
> This may be freely redistributed under the terms of the GNU Public License.
> usage: alternatives --install <link> <name> <path> <priority>
> [--initscript <service>]
> [--slave <link> <name> <path>]*
> alternatives --remove <name> <path>
> alternatives --auto <name>
> alternatives --config <name>
> alternatives --display <name>
> alternatives --set <name> <path>
> common options: --verbose --test --help --usage --version
> --altdir <directory> --admindir <directory>{noformat}
> Workaround: To get the instructions to work, I added a priority number to the end of each 'alternatives install' command as per the alternatives man page. For example,
> {noformat}sudo alternatives --install "/usr/bin/java" "java" "/usr/java/jdk1.6.0_37/bin/java" 2000{noformat}
> {noformat}sudo alternatives --install "/usr/bin/javac" "javac" "/usr/java/jdk1.6.0_37/bin/javac" 2000{noformat}
> {noformat}sudo alternatives --install "/usr/lib/jvm/java-1.6.0" "java_sdk_1.6.0" "/usr/java/jdk1.6.0_37" 2000{noformat}
> I was unsure what number to pick for the priority and randomly put 2000. I ran each sudo command separately.
> Also, it appears that the quotation marks are not necessary in the command.
--
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
13 years, 1 month
[JBoss JIRA] (TOOLSDOC-288) Missing instructions for simple JSP web application
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-288?page=com.atlassian.jira.plug... ]
Vlado Pakan closed TOOLSDOC-288.
--------------------------------
Verified in https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0...
> Missing instructions for simple JSP web application
> ---------------------------------------------------
>
> Key: TOOLSDOC-288
> URL: https://issues.jboss.org/browse/TOOLSDOC-288
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide
> Affects Versions: 4.0.0.Beta1
> Environment: Fedora 17 x86_64
> Reporter: Michelle Murray
> Assignee: Isaac Rooskov
> Fix For: 4.0.0.CR1
>
>
> About: JBDS Getting Started Guide 5.0.1. Chapter 9 outlines how to develop a simple JSP web application.
> Issue: I followed the steps in this chapter without issue up to section 9.2.2. This next section describes the web.xml file. It states that "When you are creating web project the wizard creates the web.xml file for you automatically." But the web.xml file had not been automatically created in my jsphello project.
> Workaround: Back in 9.1, Setting Up the Project, an extra step needs to be added to the instructions. The current final bullet point of these instructions should be split into multiple bullets as follow:
> * Then select Minimal Configuration from the list of possible configurations and click Next twice to move through the Java window to the Web Module Window.
> * Select the Generate web.xml deployment descriptor and Click Finish.
> This additional step creates a web.xml file within the WebContent/WEB_INF directory. It appears that the contents of this web.xml file fits that of the one shown in Figure 9.6.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13480) BrowserSim: simulator is closing unexpectedly while changing skin
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13480?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-13480.
-------------------------------
Verified with JBDS 6.0.1.GA GA-v20130304-0526-B338
> BrowserSim: simulator is closing unexpectedly while changing skin
> -----------------------------------------------------------------
>
> Key: JBIDE-13480
> URL: https://issues.jboss.org/browse/JBIDE-13480
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.0.0.CR1
> Environment: Windows 7
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.0.1.Final
>
>
> On some web pages BrowserSim is closing with the following stack trace while changing skin (see steps to reproduce):
> {code}
> Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4361)
> at org.eclipse.swt.SWT.error(SWT.java:4276)
> at org.eclipse.swt.SWT.error(SWT.java:4247)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:3725)
> at org.jboss.tools.vpe.browsersim.ui.skin.ios.AppleIPhone3ResizableSkin.
> progressChanged(AppleIPhone3ResizableSkin.java:247)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$3.changed(BrowserSim.jav
> a:251)
> at org.eclipse.swt.browser.WebResourceLoadDelegate.identifierForInitialR
> equest(WebResourceLoadDelegate.java:225)
> at org.eclipse.swt.browser.WebResourceLoadDelegate$1.method3(WebResource
> LoadDelegate.java:45)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback3(COMObject.java
> :92)
> at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
> at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:650)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
> at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822)
> at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2417)
> at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5152)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4598)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
> at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method)
> at org.eclipse.swt.internal.webkit.IWebView.setHostWindow(IWebView.java:
> 76)
> at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1064)
> at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:646)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:808)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:167)
> at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:
> 790)
> at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1290)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446)
> at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:448)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:715)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.setSelectedDevice(Browse
> rSim.java:673)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$11$1.update(BrowserSim.j
> ava:433)
> at java.util.Observable.notifyObservers(Unknown Source)
> at java.util.Observable.notifyObservers(Unknown Source)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$22.widgetSelected(Browse
> rSim.java:651)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
> 248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.main(BrowserSim.java:156
> )
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.swtjar.SWTLoader.main(SWTLoader.java:38)
> {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
13 years, 1 month