[JBoss JIRA] (JBDS-2749) Update screen captures in docs that explicitly reference JBDS 7.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2749?page=com.atlassian.jira.plugin.... ]
Michelle Murray resolved JBDS-2749.
-----------------------------------
Resolution: Done
> Update screen captures in docs that explicitly reference JBDS 7.0
> -----------------------------------------------------------------
>
> Key: JBDS-2749
> URL: https://issues.jboss.org/browse/JBDS-2749
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: documentation, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 7.1.0.GA
>
>
> Screen captures that will need updating for 7.1 docs
> *Installation Guide*
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
> * Figure 3.2. Installation Step 3: Select Target Folder
> * Figure 3.3. Installation Step 4: Select Java VM
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State
> * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace
> * Figure 3.7. Confirm Selected Features Window
> * Figure 3.10. Work from an Online Website
> * Figure 3.11. work from a Local Copy of the Update .zip File
> * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse
> * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace
> * Figure 6.3. Confirm Selected Features Window
> *Migration Guide*
> * Figure 3.1. jbdevstudio.ini File Open in a Text Editor
> *Getting Started Guide* (all Fig. shared with Installation Guide)
> * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal
> * Figure 3.2. Installation Step 3: Select Target Folder
> * Figure 3.3. Installation Step 4: Select Java VM
> * Figure 3.5. Installation Step 7: Installation Progress in Finished State
> *User Guide*
> * Figure 2.4. JBoss Buzz
> * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window
--
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] (TOOLSDOC-438) Document combined universal installer to include EAP 6.2
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-438:
----------------------------------------
Summary: Document combined universal installer to include EAP 6.2
Key: TOOLSDOC-438
URL: https://issues.jboss.org/browse/TOOLSDOC-438
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Installation Guide, Release Notes
Affects Versions: 4.1.1
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.1
As per JBDS-2856, combined universal installer EAP version is being bumped from 6.1.1 to 6.2.0.
Need to:
* Update item in Release Notes document
* Change info on Customer Portal supported configs page
_In event that combined universal installer is pulled, need to:_
* Remove mention of bundled installer from Release Notes document
* Change info on Customer Portal supported configs page
* Identify and remove selected text from Installation Guide sections: 3.1 Install Options, 3.2 Install JBoss Developer Studio
--
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] (TOOLSDOC-436) Awkward grammar in this section
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-436?page=com.atlassian.jira.plug... ]
Michelle Murray resolved TOOLSDOC-436.
--------------------------------------
Resolution: Done
> Awkward grammar in this section
> -------------------------------
>
> Key: TOOLSDOC-436
> URL: https://issues.jboss.org/browse/TOOLSDOC-436
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: User Guide
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 05-12-2013 12:18:09
> Topic ID: 25559-558132 [Latest]
> Reporter: Len DiMaggio
> Assignee: Michelle Murray
> Priority: Minor
>
> Title: About IDE Server Definitions
> Describe the issue:
> The text in question is:
> Server adapter
> Also referred to as simple a server, this informs the IDE about management settings for server runtime environments.
> Suggestions for improvement:
> Additional information:
--
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-16274) Forge 2 console fails to open and can't configure Forge 2 in preferences
by Robb Greathouse (JIRA)
Robb Greathouse created JBIDE-16274:
---------------------------------------
Summary: Forge 2 console fails to open and can't configure Forge 2 in preferences
Key: JBIDE-16274
URL: https://issues.jboss.org/browse/JBIDE-16274
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.1.0.Final
Environment: Eclipse Kepler on Macbook pro with 64 bit os
Reporter: Robb Greathouse
When console opens get this error.
Plug-in org.jboss.tools.forge.ui was unable to load class org.jboss.tools.forge.ui.part.ForgeView.
org.eclipse.core.runtime.CoreException: Plug-in org.jboss.tools.forge.ui was unable to load class org.jboss.tools.forge.ui.part.ForgeView.
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.eclipse.ui.internal.registry.ViewDescriptor.createView(ViewDescriptor.java:62)
at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:111)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPart(CompatibilityPart.java:266)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:304)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)
at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53)
at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$6.run(PartRenderingEngine.java:526)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:511)
at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:61)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1096)
at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:97)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:649)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:61)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:645)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:61)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:645)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:61)
at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveRenderer.processContents(PerspectiveRenderer.java:59)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:645)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.showTab(PerspectiveStackRenderer.java:103)
at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:97)
at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.postProcess(PerspectiveStackRenderer.java:77)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:649)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:61)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:645)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:61)
at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:676)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:645)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1042)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
Caused by: java.lang.ClassNotFoundException: org.jboss.tools.forge.ui.part.ForgeView cannot be found by org.jboss.tools.forge.ui_1.3.0.qualifier
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:340)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1212)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
... 110 more
--
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-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16272:
-----------------------------------
Fix Version/s: 4.2.x
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
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-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16272:
----------------------------------------
If a4j:calendar is suggested then it means you have the corresponding tag lib in your project classpath. It may come from application server you are deploying to.
Please open Web Projects View (Window->Show View->Other...->JBoss Tools Web->Web Projects) then find your project there and see all the available tag libraries under Tag Libraries node.
If there a few a4j libs? You can open this lib, press Link with Editor button in Package Explorer view to see where from this lib are.
I can't reproduce this issue if I create a JSF 2.1 project with AS 7 as a targer runtime.
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
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