May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-231) Registry accounts does not accept data with _ [EBZ#495072]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-231: --------------------------------------- Summary: Registry accounts does not accept data with _ [EBZ#495072] Key: ERT-231 URL: https://issues.jboss.org/browse/ERT-231 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot If you configure a docker registry account with hostname=hub_1.docker.com user=a email=b(a)b.com password=c then close the preference dialog and reopen it, then address is now hub, username 1.docker.com and email a. If you configure a docker registry account with hostname=hub.docker.com user=a_1 email=b(a)b.com password=c then close the preference dialog and reopen it, then address is now hub.docker.com, username a and email 1. If you configure a docker registry account with hostname=hub.docker.com user=a email=b_1(a)b.com password=c then close the preference dialog and reopen it, then address is now hub.docker.com, username a and email b. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-232) Image name validator doesn't accept image repositories with multiple / in them [EBZ#495073]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-232: --------------------------------------- Summary: Image name validator doesn't accept image repositories with multiple / in them [EBZ#495073] Key: ERT-232 URL: https://issues.jboss.org/browse/ERT-232 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) The following valid image name: docker.io/ibmiccm/rhel71:latest because the repo has multiple forward slashes in it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22159?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22159: ------------------------------------------ Story Points: 1 > Docker image is empty after selecting it from Image search wizard > ----------------------------------------------------------------- > > Key: JBIDE-22159 > URL: https://issues.jboss.org/browse/JBIDE-22159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection: > - In OpenShift Explorer, select the Deploy Image menu > - select the docker connection > - type a docker image name already pulled in the docker daemon > - delete it and click the search... button > - select the same docker image as previously typed > - once the search wizard closes, the docker Image name field is still empty. > See http://screencast.com/t/iTJX7SjB > As per [~scabanovich]: > {quote} > it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change > {quote} > and his fix proposal: > {quote} > before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue). > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22411: ------------------------------------ Do the upcoming updates need to be included in JBT 4.4.0.Alpha3 / devstudio 10.0.0.Alpha3? Or can they be picked up next week when we move to Neon.0.RC4? > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-22436: --------------------------------------- I can't reproduce the issue either on Fedora 23 Cinnamon. I have tested JBDS 9.0.0, 9.1.0 and 10.0.0. Can you always reproduce it? Is it reproducible in a new workspace? Could you attach .cheatsheet.xml from your helloworld or kitchensink project? > Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22436 > URL: https://issues.jboss.org/browse/JBIDE-22436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.1.Final > Reporter: Michal Jurc > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBIDE-22436-9.1-helloworld.log > > > After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message: > {quote}An error has occurred. See error log for more details. > java.lang.NullPointerException{quote} > The detailed error log produces the same message. > The quickstarts and their cheat sheets work even after the prompt with NullPointerException message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3904) Error logged at startup - Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3904?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3904. ------------------------------ Closing - problem is not seen in: Version: 10.0.0.Alpha3 Build id: Alpha3-v20160531-1024-B5476 Build date: 20160531-1024 > Error logged at startup - Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398 > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3904 > URL: https://issues.jboss.org/browse/JBDS-3904 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: build > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160520-1027-B5398 > Build date: 20160520-1027 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > Attachments: log.txt > > > This error is logged - and reported to the user if reporting is enabled - on every startup after installation. > The following report will be sent to JBoss Tools: > ------ > STATUS > ------ > pluginId org.eclipse.equinox.ds > pluginVersion 1.4.400.v20160226-2036 > code 0 > severity 4 > message Exception occurred while creating new instance of component Component[ > name = com.jboss.devstudio.core.usage.branding > activate = activate > deactivate = deactivate > modified = > configuration-policy = optional > factory = null > autoenable = true > immediate = true > implementation = com.jboss.devstudio.core.usage.branding.JBDSUsageBranding > state = Unsatisfied > properties = {service.ranking=1} > serviceFactory = false > serviceInterface = [org.jboss.tools.usage.branding.IUsageBranding] > references = null > located in bundle = com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398 [22] > ] > fingerprint 922db17c79f930f34d712e9c0d836079 > Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564) > at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493) > at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:270) > at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:331) > at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620) > at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197) > at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343) > at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222) > at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109) > at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862) > at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801) > at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127) > at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225) > at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464) > at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:482) > at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:999) > at org.eclipse.equinox.internal.p2.core.DefaultAgentProvider.createAgent(DefaultAgentProvider.java:43) > at org.jboss.tools.central.installation.InstallationChecker.<init>(InstallationChecker.java:66) > at org.jboss.tools.central.installation.InstallationChecker.getInstance(InstallationChecker.java:84) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$6.run(GettingStartedHtmlPage.java:327) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > ------ > REPORT > ------ > anonymousId dcf4d3ca-83df-4601-b255-94c52db993fc > name > email > comment > eclipseBuildId 10.0.0.Alpha1-v20160520-1027-B5398 > eclipseProduct com.jboss.devstudio.core.product > javaRuntimeVersion 1.8.0_65-b17 > osgiWs gtk > osgiOs Linux > osgiOsVersion 3.10.0.el7 > osgiArch x86_64 > severity UNKNOWN > ------- > BUNDLES > ------- > name org.eclipse.core.jobs > version 3.8.0.v20160319-0610 > name org.eclipse.equinox.ds > version 1.4.400.v20160226-2036 > name org.eclipse.equinox.p2.core > version 2.4.100.v20160419-0834 > name org.eclipse.osgi > version 3.11.0.v20160427-2120 > name org.jboss.tools.central > version 2.1.0.Alpha1-v20160510-1913-B866 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22469) Compilation problem in StructuredModelWrapperTest

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22469?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22469: ------------------------------------------ Attachment: CompilationProblem.png > Compilation problem in StructuredModelWrapperTest > ------------------------------------------------- > > Key: JBIDE-22469 > URL: https://issues.jboss.org/browse/JBIDE-22469 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Alpha2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > Attachments: CompilationProblem.png > > > Eclipse show error marker "The method execute(IFile, StructuredModelWrapper.ICommand) is ambiguous for the type StructuredModelWrapper". On the call > {code} > StructuredModelWrapper.execute(testFile, xmlDocument -> assertNotNull(xmlDocument)); > {code} > There are 2 execute methods, with similar interfaces. Though compiler shoud resolve the method by assertNotNull having 'void' for the return type, and tycho build currently finds no problem with it, still this code looks on the verge of fault and better be improved by changing it to > {code} > StructuredModelWrapper.execute(testFile, xmlDocument -> { assertNotNull(xmlDocument); }); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22469) Compilation problem in StructuredModelWrapperTest

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-22469: --------------------------------------------- Summary: Compilation problem in StructuredModelWrapperTest Key: JBIDE-22469 URL: https://issues.jboss.org/browse/JBIDE-22469 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.4.0.Alpha2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.4.0.Alpha3 Eclipse show error marker "The method execute(IFile, StructuredModelWrapper.ICommand) is ambiguous for the type StructuredModelWrapper". On the call {code} StructuredModelWrapper.execute(testFile, xmlDocument -> assertNotNull(xmlDocument)); {code} There are 2 execute methods, with similar interfaces. Though compiler shoud resolve the method by assertNotNull having 'void' for the return type, and tycho build currently finds no problem with it, still this code looks on the verge of fault and better be improved by changing it to {code} StructuredModelWrapper.execute(testFile, xmlDocument -> { assertNotNull(xmlDocument); }); {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-22411: --------------------------------------- RC3 is likely to be built today or tomorrow afternoon at latest. The stable-5.0 branch which will be used for Neon is putting builds into a different repo (updates-docker-nightly-neon). If you are tracking Neon, then you can use the latest build from there if you cannot wait for RC3 as it will contain more fixes. Use updates-docker-nightly if you are not tracking our official Neon release and are wanting latest/greatest/next release. Note that 0530 build won't be saved on the Linux Tools download site (only the milestone releases are saved). > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-22411: --------------------------------------- well, yes, but you might have to do the same operation again tomorrow or Thrusday once the RC3 bits are available... > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016