[JBoss JIRA] (JBIDE-13122) Check button "Every start" does not work properly
by Petr Suchý (JIRA)
Petr Suchý created JBIDE-13122:
----------------------------------
Summary: Check button "Every start" does not work properly
Key: JBIDE-13122
URL: https://issues.jboss.org/browse/JBIDE-13122
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.0.0.CR1
Environment: JBT 4.0.0.CR1 v20121118-0855-B78
Reporter: Petr Suchý
Assignee: Snjezana Peco
Fix For: 4.0.0.CR2
When I check "Every start" of some path on runtime detection preference page and then I cancel this action, after reopening the page is this check-button still checked.
--
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, 4 months
[JBoss JIRA] (JBIDE-13239) as7.1 not always starting
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-13239:
-------------------------------------------
Summary: as7.1 not always starting
Key: JBIDE-13239
URL: https://issues.jboss.org/browse/JBIDE-13239
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Environment:
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Installed AS 7.1.0
starting has it 1 out of 3 times not detecting the start.
And 1 out of 4 or so times where it cannot start I see this in the log:
org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:87)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:233)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:225)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remoting3.jmx.RemotingConnector.connect(RemotingConnector.java:155)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:71)
... 6 more
Not sure why AS71 is trying to connect via JMX when no jmx view or any such thing open/activated?
--
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, 4 months
[JBoss JIRA] (JBIDE-13066) Hard-coded cartridge name 'mongodb-2.0' in OpenShift Plugin
by Attila Nagy (JIRA)
Attila Nagy created JBIDE-13066:
-----------------------------------
Summary: Hard-coded cartridge name 'mongodb-2.0' in OpenShift Plugin
Key: JBIDE-13066
URL: https://issues.jboss.org/browse/JBIDE-13066
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Attila Nagy
The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
Additionally I'm unable to embed those cartridges. I can see the following error message.
Could not embed cartridges for application myphptesting
Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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, 4 months
[JBoss JIRA] (JBIDE-13223) test failure in org.jboss.tools.seam.ui.test.jbide.JBide3989Test.testJBide3989 (from org.jboss.tools.seam.ui.test.SeamUiAllTests) : The quickfix "Set Seam Properties" doesn't exist.
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13223:
----------------------------------
Summary: test failure in org.jboss.tools.seam.ui.test.jbide.JBide3989Test.testJBide3989 (from org.jboss.tools.seam.ui.test.SeamUiAllTests) : The quickfix "Set Seam Properties" doesn't exist.
Key: JBIDE-13223
URL: https://issues.jboss.org/browse/JBIDE-13223
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.0.0.CR1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Fix For: 4.0.0.CR1
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/59/testReport/org.jboss.tools.seam.ui.test.jbide/JBide3989Test/testJBide3989/}
Regression
org.jboss.tools.seam.ui.test.jbide.JBide3989Test.testJBide3989 (from org.jboss.tools.seam.ui.test.SeamUiAllTests)
Failing for the past 1 build (Since Unstable#59 )
Took 2.3 sec.
add description
Error Message
The quickfix "Set Seam Properties" doesn't exist.
Stacktrace
junit.framework.AssertionFailedError: The quickfix "Set Seam Properties" doesn't exist.
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.tools.seam.ui.test.jbide.JBide3989Test.testJBide3989(JBide3989Test.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){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, 4 months
[JBoss JIRA] (JBIDE-13237) Use "suggested-value" from faces-config.xml for JSF attribute suggestion
by Paul Dijou (JIRA)
Paul Dijou created JBIDE-13237:
----------------------------------
Summary: Use "suggested-value" from faces-config.xml for JSF attribute suggestion
Key: JBIDE-13237
URL: https://issues.jboss.org/browse/JBIDE-13237
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JSF
Reporter: Paul Dijou
Assignee: Alexey Kazakov
After reading [this wiki entry|https://community.jboss.org/wiki/NewKBPlug-inAndCodeAssistInJBossTo...], it looks like one property of the faces-config.xml isn't used so far, it's the *"suggested-value"* (see http://horstmann.com/corejsf/faces-config.html#suggested-value ). Its description is quite small and I couldn't find any real documentation about it. But we can read: "This value is advisory only and is intended for tools", and JBoss Tools is... a tool, right? :-)
So it would be great that JBoss Tools check the presence of such a "suggested-value" inside faces-config.xml and population an "enumeration" proposal type for the corresponding attribute.
Since "suggested-value" is a string, it cannot support natively a list of suggestions, so, right now, RichFaces is using "," as a separator. Which mean having:
{code}
<property-name>severity</property-name>
<property-class>java.lang.String</property-class>
<suggested-value>success,info,warning,important,inverse</suggested-value>
{code}
Should be equivalent to:
{code}
<attribute name="severity">
<proposal type="enumeration">
<param value="success" />
<param value="info" />
<param value="warning" />
<param value="important" />
<param value="inverse" />
</proposal>
</attribute>
{code}
What do you think?
--
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, 4 months
[JBoss JIRA] (JBIDE-13198) BrowserSim incorrect behaviour on Mac OS
by Konstantin Marmalyukov (JIRA)
Konstantin Marmalyukov created JBIDE-13198:
----------------------------------------------
Summary: BrowserSim incorrect behaviour on Mac OS
Key: JBIDE-13198
URL: https://issues.jboss.org/browse/JBIDE-13198
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Mac OS
Reporter: Konstantin Marmalyukov
Assignee: Konstantin Marmalyukov
Precondition:
Open at least two windows(open in new window action).
Condition:
When we make right-click on inactive browsersim window, on Windows and Ubuntu this window activates. The same does not happens on Mac OS.
Because of that when we close inactive window, active window closes.
--
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, 4 months
[JBoss JIRA] (JBIDE-13230) Quick fixes for problem markers for projects don't work anymore
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-13230:
--------------------------------------
Summary: Quick fixes for problem markers for projects don't work anymore
Key: JBIDE-13230
URL: https://issues.jboss.org/browse/JBIDE-13230
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.1.0.Alpha1
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 4.1.0.Alpha1
1. Create a Seam project
2. Open .project
3. Change Seam Runtime name to something that doesn't exist
4. Save the .project
5. Open the problems view
6. There is an error saying the runtime doesn't not exist
7. Run the quick fix for this problem (see pop up menu)
8. FAILURE:
{code}
org.eclipse.e4.core.di.InjectionException: org.eclipse.core.commands.ExecutionException
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:229)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:210)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:814)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:707)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:691)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:630)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
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:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
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:601)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Caused by: org.eclipse.core.commands.ExecutionException
at org.eclipse.ui.internal.views.markers.QuickFixHandler.execute(QuickFixHandler.java:128)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76)
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:601)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
... 34 more
Caused by: java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:477)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.eclipse.ui.internal.progress.ProgressManager$RunnableWithStatus.run(ProgressManager.java:1346)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.progress.ProgressManager$5.run(ProgressManager.java:1184)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4291)
at org.eclipse.ui.internal.progress.ProgressManager.runInUI(ProgressManager.java:1182)
at org.eclipse.ui.internal.progress.WorkbenchSiteProgressService.runInUI(WorkbenchSiteProgressService.java:376)
at org.eclipse.ui.internal.views.markers.QuickFixHandler.execute(QuickFixHandler.java:124)
... 41 more
Caused by: java.lang.ClassCastException: org.eclipse.core.internal.resources.Project cannot be cast to org.eclipse.core.resources.IFile
at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.getResolutions(ConfigureProblemSeverityResolutionGenerator.java:53)
at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.getResolutions(MarkerHelpRegistry.java:253)
at org.eclipse.ui.internal.views.markers.QuickFixHandler$1.run(QuickFixHandler.java:88)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
... 52 more
{code}
9. ASSERT: There should be two QFs:
- Add <...> Seam Runtime
- Set Seam properties
--
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, 4 months