August 2015 - jbosstools-issues - Jboss List Archives

[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 commented on JBIDE-20409: ------------------------------------------ [~jcantrill] not sure if [~yue.wang] really means that the console should reflect that the process was terminated (is it? isnt it?). I agree on the fact that the console view can be kept opened. > [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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20397: ------------------------------------------ [~jcantrill] I think that we should still do it since the "workaround" sounds simple and wont harm future impls. Keeping this buggy when it comes to state sounds not like a good option imho. > [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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3489: ------------------------------ Labels: openshift_v3 (was: ) > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.0.0.CR1 > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20402: -------------------------------- Labels: openshift_v3 (was: ) > Contribute "Deploy to Openshift" menu in Docker Tools' Image view > ----------------------------------------------------------------- > > Key: JBIDE-20402 > URL: https://issues.jboss.org/browse/JBIDE-20402 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > It's possible to contribute a new menu/handler to the Docker Tooling Images view. > We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift" > The following infos are required to actually be able to deploy the selected image onto OS: > - the local docker registry. OS will need a route to be able to access it > - the docker hub registry > - environment variables > - ports > - volumes > The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git > The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... > Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... > Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20099: -------------------------------- Labels: openshift_v3 (was: ) > enable a logstream for Openshift Pods > ------------------------------------- > > Key: JBIDE-20099 > URL: https://issues.jboss.org/browse/JBIDE-20099 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Diógenes Rettori > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > enable the eclipse console to show > oc get logs <pod> > oc get build-logs <build> > You click on the pod, then right-click show logs, or double click go to logs... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20203) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift]

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20203?page=com.atlassian.jira.plugi... ] Daniel Azarov reassigned JBIDE-20203: ------------------------------------- Assignee: Daniel Azarov (was: Andre Dietisheim) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift] > ------------------------------------------------------------------------------------- > > Key: JBIDE-20203 > URL: https://issues.jboss.org/browse/JBIDE-20203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Daniel Azarov > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [OpenShift]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015