[JBoss JIRA] (JBIDE-12463) git executable not found in Windows and JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12463?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12463:
------------------------------------
Need more info re: steps to reproduce. Please state which version of windows, which version of msysgit, which version of JBoss Tools / Forge, etc.
> git executable not found in Windows and JBoss Tools
> ---------------------------------------------------
>
> Key: JBIDE-12463
> URL: https://issues.jboss.org/browse/JBIDE-12463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
>
> I have msysgit installed on my machine and placed on the PATH dir. When I run the "git" command, the following is displayed:
> {code}
> [bootdemo] bootdemo $ git
> ***ERROR*** [git] Cannot run program "git" (in directory "D:\work\workspace\bootdemo"): CreateProcess error=2, The system cannot find the file specified
> {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, 6 months
[JBoss JIRA] (JBIDE-12648) Error in error log when running JSF bot tests
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-12648:
-----------------------------------
Summary: Error in error log when running JSF bot tests
Key: JBIDE-12648
URL: https://issues.jboss.org/browse/JBIDE-12648
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Environment: Linux
Reporter: Vlado Pakan
Assignee: Alexey Kazakov
When running JSF Swt Bot tests on Jenkins there is this error in ErrorLog making test to fail:
{code}
!ENTRY org.eclipse.osgi 4 0 2012-09-20 02:18:09.081
!MESSAGE Application error
!STACK 1
java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
at org.jboss.tools.common.model.ui.dnd.ModelTransfer.javaToNative(ModelTransfer.java:38)
at org.eclipse.swt.dnd.ClipboardProxy.getFunc(ClipboardProxy.java:138)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8307)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1192)
at org.eclipse.swt.internal.gtk.OS._gtk_clipboard_store(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_clipboard_store(OS.java:6338)
at org.eclipse.swt.dnd.ClipboardProxy.dispose(ClipboardProxy.java:93)
at org.eclipse.swt.dnd.ClipboardProxy$1.handleEvent(ClipboardProxy.java:52)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4192)
at org.eclipse.swt.widgets.Display.release(Display.java:3225)
at org.eclipse.swt.graphics.Device.dispose(Device.java:248)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
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:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)
{code}
This error is not present on jobs running on OSX and MS Windows either when running locally via maven.
--
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, 6 months
[JBoss JIRA] (JBIDE-12614) Code completion on item with h:dataTable fails if value point on datamodel object
by Piotr Bezpalko (JIRA)
Piotr Bezpalko created JBIDE-12614:
--------------------------------------
Summary: Code completion on item with h:dataTable fails if value point on datamodel object
Key: JBIDE-12614
URL: https://issues.jboss.org/browse/JBIDE-12614
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.1.1
Environment: Windows 7, Eclipse Juno
Reporter: Piotr Bezpalko
Assignee: Alexey Kazakov
Priority: Minor
When using data model object (eg. javax.faces.model.ListDataModel<MyClass> - bean.listDM) and h:dataTable (or rich:dataTable) Eclipse warns me on item presentation #{item.name) '"name" cannot be resolved'.
<h:dataTable var="item" value="#{bean.listDM}">
<h:column>
<h:outputText
value="#{item.name}" />
</h:column>
</h:dataTable>
If I change bean.listDM on bean.list (java.util.List<MyClass>), then no warning is displayed.
After deployment both of version works fine.
--
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, 6 months
[JBoss JIRA] (JBIDE-12696) Cannot update from JBT 4.0.0.Alpha1b to 4.0.0.Alpha2 from updatesite
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-12696:
--------------------------------------
Summary: Cannot update from JBT 4.0.0.Alpha1b to 4.0.0.Alpha2 from updatesite
Key: JBIDE-12696
URL: https://issues.jboss.org/browse/JBIDE-12696
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 4.0.0.Alpha2
Reporter: Stefan Bunciak
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.0.0.Alpha2
After adding {code}http://download.jboss.org/jbosstools/updates/JBossTools-4.0.0.Alpha2.core/{code} to available update sites:
* Not able to update via 'Check for updates' (Help - Check for updates)
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss JAX-RS Tools 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.4.0.Alpha2-v20120922-0406-B33)
Missing requirement: JBoss JAX-RS Tooling (Core) 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.core 1.4.0.Alpha2-v20120922-0406-B33) requires 'bundle org.eclipse.wst.sse.core 1.1.701' but it could not be found
Cannot satisfy dependency:
From: JBoss JAX-RS Tools 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.4.0.Alpha2-v20120922-0406-B33)
To: org.jboss.tools.ws.jaxrs.core [1.4.0.Alpha2-v20120922-0406-B33]
{code}
* Not able to update none of the components via 'Install new software' using the Alpha2 update site. E.g.
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss JAX-RS Tools 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.4.0.Alpha2-v20120922-0406-B33)
Missing requirement: JBoss JAX-RS Tooling (Core) 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.core 1.4.0.Alpha2-v20120922-0406-B33) requires 'bundle org.eclipse.wst.sse.core 1.1.701' but it could not be found
Cannot satisfy dependency:
From: JBoss JAX-RS Tools 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.4.0.Alpha2-v20120922-0406-B33)
To: org.jboss.tools.ws.jaxrs.core [1.4.0.Alpha2-v20120922-0406-B33]
{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, 6 months
[JBoss JIRA] (JBIDE-12591) Disable WTP Facelet validator for JBT JSF projects
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12591:
--------------------------------------
Summary: Disable WTP Facelet validator for JBT JSF projects
Key: JBIDE-12591
URL: https://issues.jboss.org/browse/JBIDE-12591
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JSF
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.0.0.Alpha2
WTP Facelet validator has a lot of critical bugs. We keep reporting them to Eclipse bug tracker but until it's stabilized I would disable WTP Facelet validator for JBT JSF Projects.
--
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, 6 months
[JBoss JIRA] (JBIDE-12626) org.jboss.tools.jsf.text.ext.test failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12626:
--------------------------------------
Summary: org.jboss.tools.jsf.text.ext.test failure
Key: JBIDE-12626
URL: https://issues.jboss.org/browse/JBIDE-12626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 4.0.0.Alpha2
{code}
sectestJSF2MessagesHyperlink(org.jboss.tools.jsf.text.ext.test.JSF2MessagesOpenOnTest) Time elapsed: 1.616 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong detection for offset - 914
at junit.framework.Assert.fail(Assert.java:50)
at org.jboss.tools.jsf.text.ext.test.JSFHyperlinkTestUtil.checkRegions(JSFHyperlinkTestUtil.java:119)
at org.jboss.tools.jsf.text.ext.test.JSF2MessagesOpenOnTest.testJSF2MessagesHyperlink(JSF2MessagesOpenOnTest.java:66)
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:616)
{code}
{code}
sectestELHyperlinkUIParam(org.jboss.tools.jsf.text.ext.test.JSPELHyperlinkUIParamTest) Time elapsed: 2.709 sec <<< FAILURE!
junit.framework.ComparisonFailure: Link 1 leads to a wrong editor. expected:<String.[java]> but was:<String.[class]>
at junit.framework.Assert.assertEquals(Assert.java:85)
at org.jboss.tools.jsf.text.ext.test.JSPELHyperlinkUIParamTest.doELHyperlinkUIParam(JSPELHyperlinkUIParamTest.java:131)
at org.jboss.tools.jsf.text.ext.test.JSPELHyperlinkUIParamTest.testELHyperlinkUIParam(JSPELHyperlinkUIParamTest.java:78)
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:616)
{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, 6 months
[JBoss JIRA] (JBIDE-12636) Exception in loading JSF2 model
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-12636:
---------------------------------------------
Summary: Exception in loading JSF2 model
Key: JBIDE-12636
URL: https://issues.jboss.org/browse/JBIDE-12636
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Alpha2
Caused by: java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/cdi
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:286)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2282)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:604)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
at org.eclipse.core.internal.resources.Project.build(Project.java:124)
at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.load(JSF2Project.java:257)
at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolveStorage(JSF2Project.java:243)
at org.jboss.tools.jsf.jsf2.bean.model.impl.JSF2Project.resolve(JSF2Project.java:250)
at org.jboss.tools.jsf.jsf2.bean.model.JSF2ProjectFactory.getJSF2Project(JSF2ProjectFactory.java:47)
at org.jboss.tools.jsf.jsf2.bean.model.JSF2ProjectFactory.getJSF2ProjectWithProgress(JSF2ProjectFactory.java:72)
at org.jboss.tools.jsf.jsf2.bean.el.JSF2ElResolver.resolveVariables(JSF2ElResolver.java:85)
at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:478)
at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:293)
at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolve(AbstractELCompletionEngine.java:171)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:384)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:350)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:325)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:292)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validate(ELValidator.java:211)
at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117)
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
... 12 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
13 years, 6 months