[JBoss JIRA] (JBIDE-20412) Hibernate Configuration File wizard should support multiple Hibernate versions
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20412?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-20412:
-----------------------------------
Assignee: Koen Aers
> Hibernate Configuration File wizard should support multiple Hibernate versions
> ------------------------------------------------------------------------------
>
> Key: JBIDE-20412
> URL: https://issues.jboss.org/browse/JBIDE-20412
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.3.0.CR1
>
> Attachments: current-version.png, new-version.png
>
>
> Currently Hibernate Configuration File wizard is hardcoded to use Hibernate 3.5 and appropriate version of tooling. It should support multiple Hibernate versions so appropriate Hiberante tools libs are used. Highest version of supported Hibernate (currently 4.3) should be offered by default.
--
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 3:38 PM:
------------------------------------------------------------------
I'm excluding "virt" slaves and watch if this helps.
{code:title=Jenkins Slaves Label expression}
(RHEL7||jboss-prod)&&!EAP-RHEL7&&!ia64&&!ppc64&&!rhts
{code}
was (Author: adietish):
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-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 commented on JBIDE-20414:
----------------------------------------
Currently no. You can disable it only for the project.
> 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 Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20414:
-------------------------------------
Couldn't a user just exclude particular files or folders from EL validation?
> 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 Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20414?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-20414:
-----------------------------------------------
This kind of EL syntax is supported only by MyBatis, that is it is correct only when mybatis.jar is included in class path.
Will we implement support for MyBatis?
> 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-20409) [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20409?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20409:
---------------------------------------
This is a minor annoyance. Thinking this through, I'm not sure this is a bug or an enhancement. If we close the console, you will never get the 'stop' message that is logged there. I think we should reject this. If the console is ever used to log traffic, we would have a situation where you would be unable to review the traffic if you stopped by the wizard.
> [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-20409
> URL: https://issues.jboss.org/browse/JBIDE-20409
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Environment: 3.0.0.CR1-v20150731-0236-B931
> Reporter: Yue Wang
> Assignee: Jeff Cantrill
> Priority: Minor
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.0.CR1
>
>
> Since stop port-forwarding console can stop port forwarding, port-forwarding console should be terminated when when I stop forwarding from wizard.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20397:
---------------------------------------
[~adietish] There is a PR is upstream to resolve. Given our time constraints, I don't know how much we want to delve into fixing this. Also, if when upstream moves away from SPDY, maybe we will be able to ditch the binary dependency. I don't have a good handle on the best way to resolve this since I feel like checking the error message is a patch; especially if the message changes.
> [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20397
> URL: https://issues.jboss.org/browse/JBIDE-20397
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Environment: 3.0.0.CR1-v20150728-1708-B905
> Reporter: Chunyun Chen
> Assignee: Jeff Cantrill
> Labels: application_wizard, openshift_v3, port_forwarding_wizard
> Fix For: 4.3.0.CR1
>
>
> Port forward successfully even if the relevant local port is used by other process.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20409) [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20409?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20409:
-------------------------------------
Summary: [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard (was: [origin_intservice_59]port-forwarding console should stop when I stop forwarding from wizard)
> [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-20409
> URL: https://issues.jboss.org/browse/JBIDE-20409
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Environment: 3.0.0.CR1-v20150731-0236-B931
> Reporter: Yue Wang
> Priority: Minor
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.0.CR1
>
>
> Since stop port-forwarding console can stop port forwarding, port-forwarding console should be terminated when when I stop forwarding from wizard.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months