March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23660: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM2) > CDK Server adapter should have an option to configure stop command > ------------------------------------------------------------------ > > Key: JBIDE-23660 > URL: https://issues.jboss.org/browse/JBIDE-23660 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.2.Final > Reporter: Ricardo Martinelli Oliveira > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > > CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop. > Why? > It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example: > * If I'm stopping it to save resources, then I'm loosing all my job in it. > * All images already pulled will be lost, so I cannot work offline -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23656) Missing validation of step listener with empty attribute ref

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23656?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23656: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Missing validation of step listener with empty attribute ref > ------------------------------------------------------------ > > Key: JBIDE-23656 > URL: https://issues.jboss.org/browse/JBIDE-23656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.Final > Reporter: Ondrej Dockal > Priority: Minor > Fix For: 4.4.4.AM3 > > Attachments: batch-test-project.zip > > > There is missing warning in listener's tag with empty reference in source view. Empty value of reference attribute in step listener should show warning like job listener does when there is empty ref: "Job listener is expected". Please, add warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Pushing Image into Openshift registry fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23771: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM2) > Pushing Image into Openshift registry fails > ------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23827) Move docker.redder plugin from jbosstools-integration-tests to eclipse (upstream)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23827?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23827: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM2) > Move docker.redder plugin from jbosstools-integration-tests to eclipse (upstream) > --------------------------------------------------------------------------------- > > Key: JBIDE-23827 > URL: https://issues.jboss.org/browse/JBIDE-23827 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, integration-tests > Reporter: Pavol Srna > Assignee: Josef Kopriva > Fix For: 4.4.4.Final > > > Tracked here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510754 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23861) CDI support is not enabled automatically with JBoss AS 7.1 runtime

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23861?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23861: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > CDI support is not enabled automatically with JBoss AS 7.1 runtime > ------------------------------------------------------------------ > > Key: JBIDE-23861 > URL: https://issues.jboss.org/browse/JBIDE-23861 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.4.3.AM2 > Environment: Devstudio AM2-v20170127-1155-B6970, Java 1.8.0_111-b15, JBoss AS 7.1.1.Final > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.4.4.AM3 > > Attachments: CdiSupport1.png, CdiSupport2.png > > > When I create a Dynamic Web Project or EJB Project the CDI support should be enabled automatically. It works properly when I have JBoss EAP 7 or Wildfly 10 as target platform, but it doesn't work with JBoss AS 7.1. > There is no error in the log, there is only warning in the problems view. > ??JBoss Tools Knowledge Base probelm: Nature/Builder is not installed on project. Use quick fix to enable %KB_REQUIRED_FOR_FACET and Faceted (test environment only) Content Assistant and Validation.?? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23924: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23891) EL syntax error: Expecting Expression on EL string concat operator

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23891?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23891: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM2) > EL syntax error: Expecting Expression on EL string concat operator > ------------------------------------------------------------------ > > Key: JBIDE-23891 > URL: https://issues.jboss.org/browse/JBIDE-23891 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.2.Final > Environment: Windows 10 > Eclipse Neon.2 (4.6.2) > JBoss Tools 4.4.2.Final (Marketplace) > JavaEE 7 > Reporter: thatsIch thatsIch > Priority: Minor > Fix For: 4.4.4.Final > > > The EL 3.0 specification [1] states > String Concatenation Operator - A += B > To evaluate A += B > ■ Coerce A and B to String. > ■ Return the concatenated string of A and B. > Used on a JSF Tag like > {code:java} > <h:outputText value="#{'foo' += 'bar'}" /> > {code} > leads to following warning: > *EL syntax error: Expecting expression.* > on the *=* part of the *+=* operator. > [1] http://download.oracle.com/otn-pub/jcp/el-3_0-fr-eval-spec/EL3.0.FR.pdf -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24030) Provider and plug-in name of org.boss.tools.openshift.common.core are displaying localization key

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24030?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24030: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Provider and plug-in name of org.boss.tools.openshift.common.core are displaying localization key > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-24030 > URL: https://issues.jboss.org/browse/JBIDE-24030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Priority: Optional > Fix For: 4.4.4.AM3 > > Attachments: image-2017-03-06-16-35-55-977.png, installed-bundles.png > > > !image-2017-03-06-16-35-55-977.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24025) AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24025?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24025: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder > --------------------------------------------------------------------- > > Key: JBIDE-24025 > URL: https://issues.jboss.org/browse/JBIDE-24025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Automated Error Reporting Bot > Labels: openshift_v2 > Fix For: 4.4.4.AM3 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDefaultDeployFolder(ExpressServerUtils.java:292) > at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:264) > at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:260) > at org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection.initWidgets(ExpressServerEditorSection.java:122) > at org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection$1.run(ExpressServerEditorSection.java:103) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.1.v20160907-0248 | > | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.9.0.v201610211907 | > | org.jboss.tools.openshift.express.core | 3.1.0.Final-v20160414-0041-B272 | 3.3.2.v20170119-1710 | > | org.jboss.tools.openshift.express.ui | 3.1.0.Final-v20160414-0041-B272 | 3.3.1.v20161003-1104 | > Operating Systems: > | Linux | 3.13.0 | 3.13.0 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/56df0c0fe4b0e0c18a6... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE muse be start with admin rights

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24084: ---------------------------------- Fix Version/s: 4.4.4.AM2 > To succesfully start CDKv3 Server adapter with hyperV provider, IDE muse be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.4.AM2 > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE. > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly. > Following steps to reproduce will lead to successfully started CDK3 server adapter in IDE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2017