[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Chunyun Chen (JIRA)
Chunyun Chen created JBIDE-18696:
------------------------------------
Summary: Application wizard: Can not show quickstarts list
Key: JBIDE-18696
URL: https://issues.jboss.org/browse/JBIDE-18696
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Final
Environment: Windows 8 + Eclipse Luna (4.4)
Reporter: Chunyun Chen
The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18695) Internal Error when removing an entity with Forge (CLI)
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18695:
-------------------------------------
Summary: Internal Error when removing an entity with Forge (CLI)
Key: JBIDE-18695
URL: https://issues.jboss.org/browse/JBIDE-18695
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.Final
Reporter: Xavier Coulon
I got the following error when removing a JPA entity with forge ({{rm <Entity>.java}}:
{code}
org.eclipse.core.internal.resources.ResourceException: Resource '/conferences/src/main/java/org/conferences/model/Session.java' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
at org.eclipse.core.internal.resources.Resource.findMaxProblemSeverity(Resource.java:1051)
at org.eclipse.jdt.ui.ProblemsLabelDecorator.getPackageErrorTicksFromMarkers(ProblemsLabelDecorator.java:337)
at org.eclipse.jdt.ui.ProblemsLabelDecorator.computeAdornmentFlags(ProblemsLabelDecorator.java:212)
at org.eclipse.jdt.internal.ui.viewsupport.TreeHierarchyLayoutProblemsDecorator.computePackageAdornmentFlags(TreeHierarchyLayoutProblemsDecorator.java:47)
at org.eclipse.jdt.internal.ui.viewsupport.TreeHierarchyLayoutProblemsDecorator.computeAdornmentFlags(TreeHierarchyLayoutProblemsDecorator.java:56)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerProblemsDecorator.computeAdornmentFlags(PackageExplorerProblemsDecorator.java:35)
at org.eclipse.jdt.ui.ProblemsLabelDecorator.decorateImage(ProblemsLabelDecorator.java:170)
at org.eclipse.jdt.internal.ui.viewsupport.JavaUILabelProvider.decorateImage(JavaUILabelProvider.java:134)
at org.eclipse.jdt.internal.ui.viewsupport.JavaUILabelProvider.getImage(JavaUILabelProvider.java:149)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerLabelProvider.getImage(PackageExplorerLabelProvider.java:140)
at org.eclipse.jdt.internal.ui.navigator.JavaNavigatorLabelProvider.getImage(JavaNavigatorLabelProvider.java:128)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.findImage(NavigatorContentServiceLabelProvider.java:197)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getColumnImage(NavigatorContentServiceLabelProvider.java:105)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getImage(NavigatorContentServiceLabelProvider.java:98)
at org.eclipse.ui.internal.navigator.NavigatorDecoratingLabelProvider$StyledLabelProviderAdapter.getImage(NavigatorDecoratingLabelProvider.java:59)
at org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.getImage(DelegatingStyledCellLabelProvider.java:195)
at org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.getImage(DecoratingStyledCellLabelProvider.java:173)
at org.eclipse.ui.navigator.CommonNavigatorManager.updateStatusBar(CommonNavigatorManager.java:308)
at org.eclipse.ui.navigator.CommonNavigatorManager$1.selectionChanged(CommonNavigatorManager.java:74)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1708)
at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1093)
at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:375)
at org.eclipse.ui.navigator.CommonNavigator.selectReveal(CommonNavigator.java:383)
at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.expandInProjectExplorer(CommandLineListener.java:217)
at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.expandWorkspaceResource(CommandLineListener.java:191)
at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.selectFile(CommandLineListener.java:175)
at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.selectResource(CommandLineListener.java:136)
at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.access$5(CommandLineListener.java:133)
at org.jboss.tools.forge.ui.internal.cli.CommandLineListener$1.run(CommandLineListener.java:99)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
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:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18679) JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18679?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-18679:
---------------------------------------
[~adietish] it seems that REST API provide in json key-value pairs supported_scales_from and supported_scales_to. Non-scalable applications have values 1 and 1, but scalable application has 1 and -1 (maybe there also could be some maximum number occured, need more exploration). I think it could check whether *from and *to are same or not...
To 2.: There is JIRA JBIDE-16040 for this. The haproxy should not be listed there.
> JBDS IDE for Creating New Openshift Application does not differentiate between cartridges that support scaling and cartridges that do not support scaling.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18679
> URL: https://issues.jboss.org/browse/JBIDE-18679
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.CR2
> Environment: JBDS IDE CR02 release, Open Shift Wizard - to create new openshift applications.
> Reporter: Aakanksha Singh
> Priority: Minor
> Fix For: 4.3.x
>
>
> When I create a new openshift application using Openshift Application wizard, the application creation fails.
> If i choose a cartidge without knowing if it is scalable, my application is not created due to the following reasons.
> 1. I choose a cartridge, for example diy-0.1 and proceed to select the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is not scalable.
> Error message:
> "Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: The cartridge 'diy-0.1' does not support being made scalable."
> 2. I choose a cartridge, for example haproxy-1.4 and proceed without selecting the "Enable scaling " feature in the wizard. My app is not created as the cartiridge is scalable.
> Error message:
> 1]Error Message:
> "Could not create application aakanksha
> Could not request https://openshift.redhat.com/broker/rest/domain/aakanksha/applications?in...: haproxy-1.4 cannot be added to existing applications. It is automatically added when you create a scaling application."
> Change requested:
> Somewhere in the UI the "enable scaling" and the list of cartridges should be linked.
> So If user selects a cartridge is not scalable and selects "Enable scaling" feature, the UI shows a warning sign.
> OR
> Once user selects "Enable scaling", only the list of cartridges that are scalable should be displayed in the UI and viceversa.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBTIS-343) Remove obsolete project examples for ESB (SOA-P 4.3)
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-343:
----------------------------------
Summary: Remove obsolete project examples for ESB (SOA-P 4.3)
Key: JBTIS-343
URL: https://issues.jboss.org/browse/JBTIS-343
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Components: ESB
Affects Versions: 8.0.0.Alpha2
Reporter: Tomáš Sedmík
Priority: Minor
In _File --> New --> Example... --> JBoss Tools --> Project Examples_ is obsolete category _ESB for JBoss Enterprise SOA Platform 4.3_ (see attachment). IMHO it should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3195) Problem with Download/Setup instructions of JBDS 8
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3195?page=com.atlassian.jira.plugin.... ]
David Hladky updated JBDS-3195:
-------------------------------
Description:
I am quoting: https://engineering.redhat.com/rt/Ticket/Display.html?id=321585. Please, see the ticket there, its creator added several screenshots.
-------------------------------
Page: http://www.jboss.org/products/devstudio/get-started [Open URL]
It instructs to download:
1. Download JBoss Developer Studio 8.0.0.GA Installer With EAP
<http://www.jboss.org/download-manager/file/jboss-devstudio-8.0.0.GA-jar_u... [Open URL]>.
Or See all downloads <http://www.jboss.org/products/devstudio/download [Open URL]>.
then to
1. Select the *Software/Update* tab in the *JBoss Central* view.
2.
Scroll down the list of *available features*, looking for the *JBoss
Developer Studio Integration Stack* section. See the image below.
3.
Tick the following items:
-
JBoss Business Process and Rules Development
-
JBoss Data Virtualization Development
-
JBoss Integration and SOA Development
-
JBoss SOA 5.x Development
except they are not listed in the available features.... all I can see is
what's in the following screen shots
So are the instructions related to *JBoss Developer Studio Integration
Stack* outdated, not applicable to JBDS 8? can JDBS 8 used with BPMS 6.0.3?
Many thanks
Andrea Ubbiali
SA Red Hat
was:
I am quoting: https://engineering.redhat.com/rt/Ticket/Display.html?id=321585
-------------------------------
Page: http://www.jboss.org/products/devstudio/get-started [Open URL]
It instructs to download:
1. Download JBoss Developer Studio 8.0.0.GA Installer With EAP
<http://www.jboss.org/download-manager/file/jboss-devstudio-8.0.0.GA-jar_u... [Open URL]>.
Or See all downloads <http://www.jboss.org/products/devstudio/download [Open URL]>.
then to
1. Select the *Software/Update* tab in the *JBoss Central* view.
2.
Scroll down the list of *available features*, looking for the *JBoss
Developer Studio Integration Stack* section. See the image below.
3.
Tick the following items:
-
JBoss Business Process and Rules Development
-
JBoss Data Virtualization Development
-
JBoss Integration and SOA Development
-
JBoss SOA 5.x Development
except they are not listed in the available features.... all I can see is
what's in the following screen shots
So are the instructions related to *JBoss Developer Studio Integration
Stack* outdated, not applicable to JBDS 8? can JDBS 8 used with BPMS 6.0.3?
Many thanks
Andrea Ubbiali
SA Red Hat
> Problem with Download/Setup instructions of JBDS 8
> --------------------------------------------------
>
> Key: JBDS-3195
> URL: https://issues.jboss.org/browse/JBDS-3195
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Reporter: David Hladky
>
> I am quoting: https://engineering.redhat.com/rt/Ticket/Display.html?id=321585. Please, see the ticket there, its creator added several screenshots.
> -------------------------------
> Page: http://www.jboss.org/products/devstudio/get-started [Open URL]
> It instructs to download:
> 1. Download JBoss Developer Studio 8.0.0.GA Installer With EAP
> <http://www.jboss.org/download-manager/file/jboss-devstudio-8.0.0.GA-jar_u... [Open URL]>.
> Or See all downloads <http://www.jboss.org/products/devstudio/download [Open URL]>.
> then to
> 1. Select the *Software/Update* tab in the *JBoss Central* view.
> 2.
> Scroll down the list of *available features*, looking for the *JBoss
> Developer Studio Integration Stack* section. See the image below.
> 3.
> Tick the following items:
> -
> JBoss Business Process and Rules Development
> -
> JBoss Data Virtualization Development
> -
> JBoss Integration and SOA Development
> -
> JBoss SOA 5.x Development
> except they are not listed in the available features.... all I can see is
> what's in the following screen shots
> So are the instructions related to *JBoss Developer Studio Integration
> Stack* outdated, not applicable to JBDS 8? can JDBS 8 used with BPMS 6.0.3?
> Many thanks
> Andrea Ubbiali
> SA Red Hat
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months