December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-12365) Enable JBoss Tools Knowledge Base support for dependencies

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12365?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-12365: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Enable JBoss Tools Knowledge Base support for dependencies > ---------------------------------------------------------- > > Key: JBIDE-12365 > URL: https://issues.jboss.org/browse/JBIDE-12365 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 3.3.0.Final > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: LATER > > > Suppose we have two maven projects. > One is CDI/Seam/JSF (any kind of project that requires KB builder/nature). > The other is a plain java project. > The first one includes the second one as a dependency. > When our maven intergration plugins enables CDI/Seam/JSF they also should enable KB support for all the dependencies (direct or indirect ones). > You can enable KB via org.jboss.tools.jst.web.kb.WebKbPlugin.enableKB(IProject project, IProgressMonitor monitor) > So CDI/Seam/JSF (KB included) should be enabled for the first project. > And KB should be enabled for the second one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3882) Too much querying if Usage Reporting is enabled

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3882?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3882: ------------------------------------ Assignee: Jeff MAURY (was: Alexey Kazakov) > Too much querying if Usage Reporting is enabled > ----------------------------------------------- > > Key: JBDS-3882 > URL: https://issues.jboss.org/browse/JBDS-3882 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: usage > Affects Versions: 8.1.0.GA > Environment: JBDS with Teiid Designer Plugin 9.0.6. > Windows 7 Enterprise > Machine is locked down by domain administrators, and I do not have an admin account for full privileges. > Reporter: Steve Tran > Assignee: Jeff MAURY > Fix For: 10.x > > Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG, Capture4.PNG > > > Seems like there's a lot of querying to check if Usage Reporting is enabled. Not sure why it's taking so long, or why it needs to ask so many times. I've disabled Usage Reporting, so I would assume it would come back fast when it's set to No. > This is something I usually ignore, but is problem-some when the clients keep pointing out how slow JBDS is because of this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22228: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > NPE when deploying to Openshift EAP > ----------------------------------- > > Key: JBIDE-22228 > URL: https://issues.jboss.org/browse/JBIDE-22228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Jeff MAURY > Fix For: 4.4.x > > > When I try to publish to an EAP in the CDK, I get a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12388) investigate converting usage dialog to modeless while still appearing in front of the main window

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12388?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-12388: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > investigate converting usage dialog to modeless while still appearing in front of the main window > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-12388 > URL: https://issues.jboss.org/browse/JBIDE-12388 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: LATER > > > would be interesting to see if usage dialog could be made modeless instead of modal to avoid blocking startups, especially during testing. > Previously we did not attemp this because the modeless dialog acted differently across OS's (mac and linux in particular) - maybe Juno SWT changes fixed this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20493) jbossdevstudio.app keeps crashing while adding a direct-vm component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20493?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20493: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > jbossdevstudio.app keeps crashing while adding a direct-vm component > -------------------------------------------------------------------- > > Key: JBIDE-20493 > URL: https://issues.jboss.org/browse/JBIDE-20493 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform, upstream > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio > Version: 8.1.0.GA > Build id: GA-v20150327-1349-B467 > Build date: 20150327-1349 > Reporter: Scott Stark > Assignee: Jeff MAURY > Fix For: 4.3.x > > Attachments: hs_err_pid4526.log, hs_err_pid4624.log, hs_err_pid4862.log, jbosstools-diagnostics-20150823100812.zip, jbosstools-diagnostics-20150823125246.zip, workspace2.zip > > > The jbossdevstudio.app keeps crashing while using the visual designer to edit camel routes. This has happened 4 or 5 times in the past day. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17812) "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17812?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17812: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery > --------------------------------------------------------------------------------- > > Key: JBIDE-17812 > URL: https://issues.jboss.org/browse/JBIDE-17812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Reporter: Ron Šmeral > Assignee: Jeff MAURY > Fix For: LATER > > > JBDS shows _No bean is eligible for injection to the injection point_ warning for injection points where the beans are provided by an extension in the ABD event: > {code:java|title=ByIdExtensionTest.java} > @Inject @ById("rbenevides") > private Person rafael; > {code} > * shows _No bean is eligible for injection to the injection point \[JSR-299 §5.2.1\]_ > {code:java|title=ByIdExtension.java} > public void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) { > for (final String idValue : ids) { > BeanBuilder<Person> beanBuilder = new BeanBuilder<Person>(bm) > .beanClass(Person.class) > .types(Person.class, Object. > .qualifiers(new ByIdLiteral(idValue)) > .beanLifecycle(new PersonContextualLifecycle(idValue)); > abd.addBean(beanBuilder.create()); > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4476) Import taglib in JBoss Tools Palette without the need to create a project.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4476?page=com.atlassian.jira.plugin... ] Alexey Kazakov reassigned JBIDE-4476: ------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Import taglib in JBoss Tools Palette without the need to create a project. > -------------------------------------------------------------------------- > > Key: JBIDE-4476 > URL: https://issues.jboss.org/browse/JBIDE-4476 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing > Environment: JBDS 2 > Reporter: Joao Viragine > Assignee: Jeff MAURY > Fix For: LATER > > > It would be great if we could import a taglib in JBoss Tools Palette without the need to create a project like described here: http://docs.jboss.org/tools/3.0.1.GA/en/jsf/html_single/index.html#Adding... > Just point to a tld or jar file is far enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22739: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19023) CDI validation cannot find beans in src/test to be used for injection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19023?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19023: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > CDI validation cannot find beans in src/test to be used for injection > --------------------------------------------------------------------- > > Key: JBIDE-19023 > URL: https://issues.jboss.org/browse/JBIDE-19023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Jason Porter > Assignee: Jeff MAURY > Fix For: 4.3.x > > > While trying to fix BZ1178874 I discovered that classes in src/test are not picked up as being valid beans to satisfy injection points. In the example in the Bugzilla issue (https://github.com/jboss-developer/jboss-eap-quickstarts/commit/7aa69072e...) it's a public static class being used, but even if that class is split off into its own public class it still isn't found as a valid bean. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16107) Improve portlet component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16107?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16107: -------------------------------------- Assignee: Jeff MAURY (was: Alexey Kazakov) > Improve portlet component > ------------------------- > > Key: JBIDE-16107 > URL: https://issues.jboss.org/browse/JBIDE-16107 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: portal-gatein > Affects Versions: 4.1.1.CR1 > Reporter: Snjezana Peco > Assignee: Jeff MAURY > Fix For: LATER > > > Currently, the portlet component supports (or it should support) the following runtimes: > - JBoss Portal 2.7 > - EPP 4.3/5.0/5.1/5.2 > - GateIn 3.x > - JPP 6.x > There are three facets: > - Java Portlet > - JSF Portlet > - Seam Portlet > The required libraries are the following: > Java Portlet > - requires portlet-api that is, currently, correctly recognized for some of the above mentioned runtimes. > However, there is no rule how this library would be recognized, which means it could be broken in some new runtime. > JSF Portlet > - requires portletbridge and, optionaly, richfaces libraries > Those libraries can be added from the server runtimes or a user can use his own distribution that can be added to the JSF Portlet wizard page. > If a user creates a Seam portlet and selects his richfaces distribution, the richfaces libraries added with the seam facet will be replaced with the user's library because we can't have two richfaces versions in the application. > If a user doesn't select his richfaces distribution, the richfaces libraries from Seam will be used. > Currently, there is no rule for adding those libraries. Different server runtimes contain the libraries in different locations. Portletbridge and richfaces distributions also have different structure. > Seam Portlet > The Seam portlet uses the standard seam facet and configures web.xml. > I have tried to deploy and run the seam portlet on JPP 6.1 using the Seam 2.3.2 version from WFK. > It can be deployed and run. The home page is opened, but I am not sure if all the features work correctly. > Seam 2.3.2 works properly on EAP 6.1, AS 7.1.1, AS 7.2.0.Final. > Seam 2.3.1 (the latest community version) requires adding the guava module to the jboss-deployment-structure.xml. > If a user selects the JBoss Maven Integration facet, the portlet component will create a maven project. It is possible to add portletbridge 2.0.0 as a maven artifact. > We would probably have to improve this feature. > We would have to define the following: > - what server runtimes we want to support in the future (AS 7+ runtimes GateIn 3.5/3.6, JPP > - what kinds of portlets we would support(Java portlet, JSF portlet, JSF Richfaces... not sure for Seam) > - how the required libraries (portletbridge, richfaces...) would be added. Is there a rule how they are placed to the server? > - if we will support only a mavenized portlet (all GateIn 3.6, JPP 6.1 quickstarts are maven projects) > If we decide to support only mavenized portlets, adding libraries would be much simpler. A user would only need to choose versions, i.e., to define different Maven libraries containers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016