[JBoss JIRA] (JBIDE-20414) El syntax error on mybatis mapper file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20414:
-----------------------------------
Workaround Description:
Use quickfix or disable EL syntax validation directly in Preferences:
!workaroud.png|thumbnail!
Workaround: Workaround Exists
> El syntax error on mybatis mapper file
> --------------------------------------
>
> Key: JBIDE-20414
> URL: https://issues.jboss.org/browse/JBIDE-20414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.2.Final
> Environment: Eclipse Kepler
> Reporter: Olivier LE JACQUES
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.CR1
>
> Attachments: workaround.png
>
>
> Hello,
> On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
> On mybatis mapper file .xml I have an el warning :
> EL syntax error: Expecting '}'. when I have a parameter like this :
> {code}#{nodeName, javaType=String, jdbcType=VARCHAR}{code}, in a query.
> Regards, Olivier
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20414) El syntax error on mybatis mapper file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20414:
-----------------------------------
Attachment: workaround.png
> El syntax error on mybatis mapper file
> --------------------------------------
>
> Key: JBIDE-20414
> URL: https://issues.jboss.org/browse/JBIDE-20414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.2.Final
> Environment: Eclipse Kepler
> Reporter: Olivier LE JACQUES
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.CR1
>
> Attachments: workaround.png
>
>
> Hello,
> On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
> On mybatis mapper file .xml I have an el warning :
> EL syntax error: Expecting '}'. when I have a parameter like this :
> {code}#{nodeName, javaType=String, jdbcType=VARCHAR}{code}, in a query.
> Regards, Olivier
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20414) El syntax error on mybatis mapper file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20414:
--------------------------------------
Fix Version/s: 4.3.0.CR1
Assignee: Viacheslav Kabanovich
Sprint: 03-Aug >> 16-Aug 2015-JBDS/J 2
Affects Version/s: 4.1.2.Final
I can reproduce this issue in JBT 4.3.0.Beta2 (Eclipse Mars) with any XML if this EL is used in an attribute:
{code}
<tag a="#{nodeName, javaType=String, jdbcType=VARCHAR}"></tag>
{code}
> El syntax error on mybatis mapper file
> --------------------------------------
>
> Key: JBIDE-20414
> URL: https://issues.jboss.org/browse/JBIDE-20414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.2.Final
> Environment: Eclipse Kepler
> Reporter: Olivier LE JACQUES
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.CR1
>
>
> Hello,
> On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
> On mybatis mapper file .xml I have an el warning :
> EL syntax error: Expecting '}'. when I have a parameter like this :
> {code}#{nodeName, javaType=String, jdbcType=VARCHAR}{code}, in a query.
> Regards, Olivier
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20414) El syntax error on mybatis mapper file
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20414:
-------------------------------------
Olivier, can you provide a sample project to help us reproduce the issue?
Could you attach your eclipse config (About Eclipse > Installation details > Configuration tab)
Can you reproduce the problem on Eclipse Mars, using the JBoss Tools plugins for Mars (http://marketplace.eclipse.org/content/jboss-tools)?
> El syntax error on mybatis mapper file
> --------------------------------------
>
> Key: JBIDE-20414
> URL: https://issues.jboss.org/browse/JBIDE-20414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Environment: Eclipse Kepler
> Reporter: Olivier LE JACQUES
>
> Hello,
> On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
> On mybatis mapper file .xml I have an el warning :
> EL syntax error: Expecting '}'. when I have a parameter like this :
> {code}#{nodeName, javaType=String, jdbcType=VARCHAR}{code}, in a query.
> Regards, Olivier
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20414) El syntax error on mybatis mapper file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20414:
-----------------------------------
Description:
Hello,
On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
On mybatis mapper file .xml I have an el warning :
EL syntax error: Expecting '}'. when I have a parameter like this :
{code}#{nodeName, javaType=String, jdbcType=VARCHAR}{code}, in a query.
Regards, Olivier
was:
Hello,
On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
On mybatis mapper file .xml I have an el warning :
EL syntax error: Expecting '}'. when I have a parameter like this :
#{nodeName, javaType=String, jdbcType=VARCHAR}, in a query.
Regards, Olivier
> El syntax error on mybatis mapper file
> --------------------------------------
>
> Key: JBIDE-20414
> URL: https://issues.jboss.org/browse/JBIDE-20414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Environment: Eclipse Kepler
> Reporter: Olivier LE JACQUES
>
> Hello,
> On a jsf 2.1 project with jboss tools plugin on eclipse kepler. I use mybatis.
> On mybatis mapper file .xml I have an el warning :
> EL syntax error: Expecting '}'. when I have a parameter like this :
> {code}#{nodeName, javaType=String, jdbcType=VARCHAR}{code}, in a query.
> Regards, Olivier
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20389:
------------------------------------------
I'm excluding "virt" slaves and watch if this helps.
!exclude-virt.png!
> Jenkins: inconsistent, regular test failures in openshift/egit
> --------------------------------------------------------------
>
> Key: JBIDE-20389
> URL: https://issues.jboss.org/browse/JBIDE-20389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.0.CR1
>
> Attachments: build-failures.png, exclude-virt.png, jenkins-sane.png, openshift-builds.png
>
>
> Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build.
> {quote}
> Build #33
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote
> {quote}
> {quote}
> Build #34:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject
> {quote}
> {quote}
> Build #35
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite)
> Failing for the past 1 build (Since Unstable#35 )
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20389 at 8/4/15 7:17 AM:
------------------------------------------------------------------
test failures started to happen again, reopening:
!build-failures.png!
* [#934|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/934/]:
{quote}
canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.25 sec <<< ERROR!
java.lang.IllegalArgumentException: Cannot commit project to repository.
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.jboss.tools.openshift.egit.core.EGitUtils.commit(EGitUtils.java:392)
at org.jboss.tools.openshift.egit.core.EGitUtils.commit(EGitUtils.java:399)
at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject(EGitUtilsTest.java:115)
{quote}
* [#931|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/931]:
{quote}
removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.269 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.removedButNotCommittedIsDirty(EGitUtilsTest.java:334)
{quote}
* [#932|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/932]:
is not related to this issue, it's a different test failure.
not sure yet if related, but the failures all happened when building on "virt" slaves which usually take much more time to build than "rhel" slaves.
was (Author: adietish):
test failures started to happen again, reopening:
!build-failures.png!
* [#934|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/934/]:
{quote}
canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.25 sec <<< ERROR!
java.lang.IllegalArgumentException: Cannot commit project to repository.
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.jboss.tools.openshift.egit.core.EGitUtils.commit(EGitUtils.java:392)
at org.jboss.tools.openshift.egit.core.EGitUtils.commit(EGitUtils.java:399)
at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject(EGitUtilsTest.java:115)
{quote}
* [#931|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/931]
{quote}
removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.269 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.removedButNotCommittedIsDirty(EGitUtilsTest.java:334)
{quote}
* [#932|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/932]
is not related to this issue, it's a different test failure.
not sure yet if related, but the failures all happened when building on "virt" slaves which usually take much more time to build than "rhel" slaves.
> Jenkins: inconsistent, regular test failures in openshift/egit
> --------------------------------------------------------------
>
> Key: JBIDE-20389
> URL: https://issues.jboss.org/browse/JBIDE-20389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.0.CR1
>
> Attachments: build-failures.png, jenkins-sane.png, openshift-builds.png
>
>
> Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build.
> {quote}
> Build #33
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote
> {quote}
> {quote}
> Build #34:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject
> {quote}
> {quote}
> Build #35
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite)
> Failing for the past 1 build (Since Unstable#35 )
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20389 at 8/4/15 7:16 AM:
------------------------------------------------------------------
test failures started to happen again, reopening:
!build-failures.png!
* [#934|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/934/]:
{quote}
canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.25 sec <<< ERROR!
java.lang.IllegalArgumentException: Cannot commit project to repository.
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.jboss.tools.openshift.egit.core.EGitUtils.commit(EGitUtils.java:392)
at org.jboss.tools.openshift.egit.core.EGitUtils.commit(EGitUtils.java:399)
at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject(EGitUtilsTest.java:115)
{quote}
* [#931|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/931]
{quote}
removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.269 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.removedButNotCommittedIsDirty(EGitUtilsTest.java:334)
{quote}
* [#932|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/932]
is not related to this issue, it's a different test failure.
not sure yet if related, but the failures all happened when building on "virt" slaves which usually take much more time to build than "rhel" slaves.
was (Author: adietish):
test failures started to happen again, reopening:
!build-failures.png!
> Jenkins: inconsistent, regular test failures in openshift/egit
> --------------------------------------------------------------
>
> Key: JBIDE-20389
> URL: https://issues.jboss.org/browse/JBIDE-20389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.0.CR1
>
> Attachments: build-failures.png, jenkins-sane.png, openshift-builds.png
>
>
> Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build.
> {quote}
> Build #33
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote
> {quote}
> {quote}
> Build #34:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject
> {quote}
> {quote}
> Build #35
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite)
> Failing for the past 1 build (Since Unstable#35 )
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months