April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21445) NullPointerException when trying to import a BuildConfig as a new application from OpenShift 3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21445?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21445. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > NullPointerException when trying to import a BuildConfig as a new application from OpenShift 3 > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21445 > URL: https://issues.jboss.org/browse/JBIDE-21445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: OSX > JBDS > OpenShift origin 1.1.0.1 > Reporter: Akram Ben Aissi > Assignee: Viacheslav Kabanovich > Priority: Blocker > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: eclipse.log > > > When trying to import a project from a BuildConfig (right clic import as new project), I get a NullPointerException after clicking Finish. > Same issue occurs when clicking next, and changing the destination folder for anything that exists or does not exist > eclipse.log is attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21929) Server adapter: incremental deployment is broken

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21929?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21929. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Server adapter: incremental deployment is broken > ------------------------------------------------ > > Key: JBIDE-21929 > URL: https://issues.jboss.org/browse/JBIDE-21929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master... > Deploy an eap basic app on openshift, > import the kitchensink code in the workspace > wait for the application to deploy and run on openshift > Issue #1 > - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project. > - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to > Issue #2 > - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard > - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink > - local change is not pushed immediately to the server. module restart happens before the change is effective. > (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20532) Deploy Docker: Allow a user to add volumes

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20532?page=com.atlassian.jira.plugi... ] Jeff Cantrill closed JBIDE-20532. --------------------------------- Resolution: Won't Do Per my discussion this will most likely not be implemented in 'oc new-app' and probably provides limited usefulness {quote}jcantril> new app question for you <jcantril> are you able to do anything with volumes and new-app <jcantril> i have an open issue in JBT to allow you to add volumes when you are deploying an image... but im not sure what that means in hind sight or if that even makes sense <bparees> new-app will create emptydir volumes for your DC if your image defines VOLUMEs in the dockerfile. <bparees> beyond that, no. you can't specify that you want volumes, mount points, PVs, etc. <jcantril> bparees so from a JBT perspective... it sounds like it doesnt make sense for it to allow you to define additional empty volumes.... agree or disagree? <jcantril> is it useful... at all? <bparees> defining empty volumes is rarely useful. <bparees> defining PVs would be useful, people ask for new-app to do it all the time (but it probably never will){quote} > Deploy Docker: Allow a user to add volumes > ------------------------------------------ > > Key: JBIDE-20532 > URL: https://issues.jboss.org/browse/JBIDE-20532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Allow a user to add volumes when deploying an image. This will probably require expanding beyond emptydir volumes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-21621 at 4/26/16 10:27 AM: ----------------------------------------------------------------- OK, [~nickboldt], can you please take this for the TP? http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0... It's a snapshot that I copied from the latest build of RedDeer master [1], build 789. I wonder, is the url that I used something that will stay there forever? I would hope so. In the past, I used development instead of snapshots, but since it's really a snapshot, I thought this would be more appropriate. But to get this new build, I had to disable the mvn deploy step for now (for deploying of reddeer archetype to nexus). I created a JIRA for that here: JBIDE-22248 [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... was (Author: mmalina): OK, [~nickboldt], can you please take this for the TP? http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0... It's a snapshot that I copied from the latest build of RedDeer master [1], build 789. I wonder, is the url that used something that will stay there forever? I would hope so. In the past, I used development instead of snapshots, but since it's really a snapshot, I thought this would be more appropriate. But to get this new build, I had to disable the mvn deploy step for now (for deploying of reddeer archetype to nexus). I created a JIRA for that here: JBIDE-22248 [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-166) Chromium Debug context menu's enabled for everything [EBZ#491480]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-166: --------------------------------------- Summary: Chromium Debug context menu's enabled for everything [EBZ#491480] Key: ERT-166 URL: https://issues.jboss.org/browse/ERT-166 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot The context menu "V8 Debugging" is available for any type of selection. I tracked this menu contribution to: "org.eclipse.wst.jsdt.chromium.debug.ui.ChromiumSourceFileActionsId.MenuId" Should filter to only *.js files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21018) compile failed in openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21018?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21018. --------------------------------- > compile failed in openshift > --------------------------- > > Key: JBIDE-21018 > URL: https://issues.jboss.org/browse/JBIDE-21018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Denis says Openshift is failing to compile in master: > {code} > [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure: > [INFO] [ERROR] <http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins...>:[41] > [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR); > [INFO] [ERROR] ^^^^^^^^^^^^^^^^ > [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field > [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22000) Server adapter: stream closed exception when debugging

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22000?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22000. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Server adapter: stream closed exception when debugging > ------------------------------------------------------ > > Key: JBIDE-22000 > URL: https://issues.jboss.org/browse/JBIDE-22000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > While testing the debugging support on the server adapter, I got the following error: > {code} > [ERROR] 2016-03-25 12:19:53,006 com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync - Could not retrieve error message from process > java.io.IOException: Stream closed > at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170) > at java.io.BufferedInputStream.read(BufferedInputStream.java:336) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.Reader.read(Reader.java:140) > at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1485) > at org.apache.commons.io.IOUtils.copy(IOUtils.java:1461) > at org.apache.commons.io.IOUtils.copy(IOUtils.java:1408) > at org.apache.commons.io.IOUtils.copy(IOUtils.java:1433) > at org.apache.commons.io.IOUtils.toString(IOUtils.java:585) > at org.apache.commons.io.IOUtils.toString(IOUtils.java:563) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.getErrorMessage(OpenShiftBinaryRSync.java:107) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.await(OpenShiftBinaryRSync.java:94) > {code} > This error happened at the same time as the deployment failed, as reported in JBIDE-21981, but since there are 2 distinct problems, we should track them in 2 separate issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22248) RedDeer master job cannot deploy archetype to nexus

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22248: --------------------------------------- BTW, to get a new build, I temporarily changed the mvn deploy step to mvn help:help. I changed it back now. > RedDeer master job cannot deploy archetype to nexus > --------------------------------------------------- > > Key: JBIDE-22248 > URL: https://issues.jboss.org/browse/JBIDE-22248 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Nick, can you take a look why mvn deploy fails here? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > It worked for us in the past. > It says: > {code} > [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 04:49 min > [INFO] Finished at: 2016-04-26T09:42:02-04:00 > [INFO] Final Memory: 19M/612M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {code} > I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team? > Cc: [~rawagner] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21875) NPE is thrown on OS 3 connection without any project on fresh start of IDE

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21875?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21875. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > NPE is thrown on OS 3 connection without any project on fresh start of IDE > -------------------------------------------------------------------------- > > Key: JBIDE-21875 > URL: https://issues.jboss.org/browse/JBIDE-21875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Blocker > Labels: connection, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When I start IDE and I have not stored password/token in secure storage for an OpenShift 3 connection, I am prompted to fill in credentials. After successfully filling in and hiting Finish button, connection is established, but if connection does not contain any project beneath it, there is NPE thrown with following stack trace > {code} > There was an error retrieving children in the OpenShift explorer > java.lang.NullPointerException > at java.util.ArrayList.<init>(ArrayList.java:177) > at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:73) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-21621: ------------------------------------- Assignee: Nick Boldt (was: Martin Malina) OK, [~nickboldt], can you please take this for the TP? http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0... It's a snapshot that I copied from the latest build of RedDeer master [1], build 789. I wonder, is the url that used something that will stay there forever? I would hope so. In the past, I used development instead of snapshots, but since it's really a snapshot, I thought this would be more appropriate. But to get this new build, I had to disable the mvn deploy step for now (for deploying of reddeer archetype to nexus). I created a JIRA for that here: JBIDE-22248 [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016