November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22584) jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22584: ------------------------------------------ [~nickboldt] how urgent/critical is this? We have noone working on central left. > jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22584 > URL: https://issues.jboss.org/browse/JBIDE-22584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, central-update > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.5.0.AM1 > > > Normally, jbosstools-central is built before jbosstools-discovery. > However, running jbosstools-central build for the first time, ran into this: > {code} > 22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s] > 22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED > 22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED > 22:43:52 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could not get content -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Or, this could be a problem w/ bootstrapping values in ide-config.properties? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22261 at 11/23/16 11:06 AM: --------------------------------------------------------------------- The action Show In > Server Log is being removed in the next iteration 4.5.0.AM1 (JBIDE-22717). was (Author: adietish): The action Show In > Server Log is being removed in the next iteration 4.5.0.AM1. > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.Final > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22269) Work with WildFly/EAP to generate unit tests on server installation layout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22269?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22269: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Work with WildFly/EAP to generate unit tests on server installation layout > -------------------------------------------------------------------------- > > Key: JBIDE-22269 > URL: https://issues.jboss.org/browse/JBIDE-22269 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-22269.mock.zip > > > A task to track work on making sure changes to EAP don't inadvertently break tools when changing directory structure or important keys we read. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22261. -------------------------------------- Resolution: Rejected The action Show In > Server Log is being removed in the next iteration 4.5.0.AM1. > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.Final > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22261: ------------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.x) > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.Final > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22878: ------------------------------------- [~mmalina] Can we go over this one? I can't replicate anything except a UI issue... and I've got upstream patches for those. But I can't replicate the actual issue he's indicating (badly named output ejb jar) > EAR deployed from DevStudio to EAP contains errorneously named ejbs > ------------------------------------------------------------------- > > Key: JBIDE-22878 > URL: https://issues.jboss.org/browse/JBIDE-22878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip > > > I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar. > When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot. > This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22878: -------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.2.Final) > EAR deployed from DevStudio to EAP contains errorneously named ejbs > ------------------------------------------------------------------- > > Key: JBIDE-22878 > URL: https://issues.jboss.org/browse/JBIDE-22878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip > > > I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar. > When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot. > This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22965: ------------------------------------------ [~dbocharov] do you what what the status of this issue currently is? > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22972) Properties: Add Queue To Events to improve performance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22972?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22972: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Properties: Add Queue To Events to improve performance > ------------------------------------------------------ > > Key: JBIDE-22972 > URL: https://issues.jboss.org/browse/JBIDE-22972 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Labels: openshift_v3, properties > Fix For: 4.5.x > > > There are concerns that unlike other openshift resources, the number of events can be large and we should limit the number we display to 50 > https://github.com/jbosstools/jbosstools-openshift/pull/1278#issuecomment... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22965: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.2.Final) > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

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 November 2016