May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25922) Runtime detection finds new cdk even if it already exists

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25922?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25922: ------------------------------- Sprint: devex #149 May 2018 > Runtime detection finds new cdk even if it already exists > --------------------------------------------------------- > > Key: JBIDE-25922 > URL: https://issues.jboss.org/browse/JBIDE-25922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.0.AM2 > > > I just noticed that sometimes if you repeatedly search for runtimes, the same cdk binary will be recognised as new again and again, creating duplicate server adapters if you click OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25922) Runtime detection finds new cdk even if it already exists

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25922?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25922: ------------------------------- Fix Version/s: 4.6.0.AM2 > Runtime detection finds new cdk even if it already exists > --------------------------------------------------------- > > Key: JBIDE-25922 > URL: https://issues.jboss.org/browse/JBIDE-25922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.0.AM2 > > > I just noticed that sometimes if you repeatedly search for runtimes, the same cdk binary will be recognised as new again and again, creating duplicate server adapters if you click OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25967) Properties view: Add OC version for OpenShift connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25967?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25967: ---------------------------------- Assignee: Jeff MAURY > Properties view: Add OC version for OpenShift connection > -------------------------------------------------------- > > Key: JBIDE-25967 > URL: https://issues.jboss.org/browse/JBIDE-25967 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: oc_binary, properties > Fix For: 4.6.0.AM2 > > > Properties view for OpenShift connection should also contains OC version, not only path to it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25967) Properties view: Add OC version for OpenShift connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25967?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25967: ------------------------------- Story Points: 10 > Properties view: Add OC version for OpenShift connection > -------------------------------------------------------- > > Key: JBIDE-25967 > URL: https://issues.jboss.org/browse/JBIDE-25967 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: oc_binary, properties > Fix For: 4.6.0.AM2 > > > Properties view for OpenShift connection should also contains OC version, not only path to it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25967) Properties view: Add OC version for OpenShift connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25967?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25967: ------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.x) > Properties view: Add OC version for OpenShift connection > -------------------------------------------------------- > > Key: JBIDE-25967 > URL: https://issues.jboss.org/browse/JBIDE-25967 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: oc_binary, properties > Fix For: 4.6.0.AM2 > > > Properties view for OpenShift connection should also contains OC version, not only path to it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25967) Properties view: Add OC version for OpenShift connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25967?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25967: ------------------------------- Sprint: devex #149 May 2018 > Properties view: Add OC version for OpenShift connection > -------------------------------------------------------- > > Key: JBIDE-25967 > URL: https://issues.jboss.org/browse/JBIDE-25967 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: oc_binary, properties > Fix For: 4.6.0.AM2 > > > Properties view for OpenShift connection should also contains OC version, not only path to it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25968) Downloaded CDK runtimes artifacts in /tmp folder are not given executable rights nor are copied into installation folder

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25968?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25968: ------------------------------- Sprint: devex #149 May 2018 > Downloaded CDK runtimes artifacts in /tmp folder are not given executable rights nor are copied into installation folder > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25968 > URL: https://issues.jboss.org/browse/JBIDE-25968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.3.Final > Environment: Fedora 27 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.6.0.AM1 > > Attachments: downloading_cdk_runtime.gif > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25971: ------------------------------- Sprint: devex #149 May 2018 > Add Red Hat Developers sign up link to CDK New Server wizard > ------------------------------------------------------------ > > Key: JBIDE-25971 > URL: https://issues.jboss.org/browse/JBIDE-25971 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: cdk_server_adapter_wizard > Fix For: 4.6.x > > Attachments: new-server-cdk.png > > > While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. > Imagine you don't have an account on developers.redhat.com yet. > You go to New Server -> CDK 3.2+. > On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. > So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. > That's issue 1. > !new-server-cdk.png! > There are also a few side issues: > 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. > 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? > 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25989) Circular reference detected for usage

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25989?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-25989. -------------------------------- Resolution: Done > Circular reference detected for usage > ------------------------------------- > > Key: JBIDE-25989 > URL: https://issues.jboss.org/browse/JBIDE-25989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.6.0.AM1 > Reporter: Martin Malina > Assignee: Jeff MAURY > > I just installed devstudio 12 nightly [1] and noticed this error in the Error Log view: > {code} > Circular reference detected trying to get service {org.jboss.tools.usage.branding.IUsageBranding}={service.id=39, service.bundleid=32, service.scope=bundle, service.ranking=1, component.name=com.jboss.devstudio.core.usage.branding, component.id=0} > stack of references: ServiceReference: {org.jboss.tools.usage.branding.IUsageBranding}={service.id=39, service.bundleid=32, service.scope=bundle, service.ranking=1, component.name=com.jboss.devstudio.core.usage.branding, component.id=0} > {code} > {code} > java.lang.Exception: stack trace > at org.apache.felix.scr.impl.ComponentRegistry.enterCreate(ComponentRegistry.java:467) > at org.apache.felix.scr.impl.BundleComponentActivator.enterCreate(BundleComponentActivator.java:809) > at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:806) > at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:212) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:210) > at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:111) > at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:45) > at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:524) > at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:461) > at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:624) > at org.osgi.util.tracker.ServiceTracker.addingService(ServiceTracker.java:416) > at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943) > at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1) > at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) > at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183) > at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:321) > at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:264) > at org.jboss.tools.usage.internal.JBossToolsUsageActivator.initBranding(JBossToolsUsageActivator.java:67) > at org.jboss.tools.usage.internal.JBossToolsUsageActivator.start(JBossToolsUsageActivator.java:58) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354) > at org.eclipse.osgi.container.Module.doStart(Module.java:581) > at org.eclipse.osgi.container.Module.start(Module.java:449) > at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468) > at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:470) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609) > at org.apache.felix.scr.impl.manager.AbstractComponentManager.initDependencyManagers(AbstractComponentManager.java:992) > at org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:1019) > at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:860) > at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:755) > at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:675) > at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:430) > at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:657) > at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:341) > at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:387) > at org.apache.felix.scr.impl.Activator.access$200(Activator.java:52) > at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:262) > at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) > at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) > at org.apache.felix.scr.impl.AbstractExtender.addingBundle(AbstractExtender.java:139) > at org.apache.felix.scr.impl.AbstractExtender.addingBundle(AbstractExtender.java:49) > at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:475) > at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:1) > at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) > at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) > at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:450) > at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908) > 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.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:230) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:137) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:129) > at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:191) > at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) > at org.eclipse.osgi.container.Module.start(Module.java:467) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > {code} > [1] devstudio-12.0.0.AM1-v20180502-0411-B2377-installer-standalone.jar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25399) Include new big features in JBoss Tools & Devstudio Marketplace descriptions

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25399?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25399. --------------------------------- Closing as OpenShift and Fuse/Camel information were added. Opening new jira for another outdated information in devstudio marketplace entry: JBIDE-25998. > Include new big features in JBoss Tools & Devstudio Marketplace descriptions > ---------------------------------------------------------------------------- > > Key: JBIDE-25399 > URL: https://issues.jboss.org/browse/JBIDE-25399 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: marketplace > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.3.Final > > > https://marketplace.eclipse.org/content/jboss-tools > {quote}JBoss Tools is an umbrella project for a set of Eclipse plugins that includes support for JBoss and related technologies, such as Hibernate, JBoss AS, CDI, Aerogear Hybrid Mobile, Apache Cordova, Docker, FeedHenry, JSF, (X)HTML, Maven, and more. This entry has the majority of JBoss Tools but does not include features that requires dependencies outside of what is common from Eclipse JEE and m2eclipse.{quote} > I think that it would be nice to add OpenShift and Apache Camel/Fuse in the description. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

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 2018