[JBoss JIRA] (JBDS-4359) Two "Spring" folders in "New" wizard
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4359?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-4359:
----------------------------------
Upstream issue. Same behavoir is show on STS. Will check on STS JIRA
> Two "Spring" folders in "New" wizard
> ------------------------------------
>
> Key: JBDS-4359
> URL: https://issues.jboss.org/browse/JBDS-4359
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 10.4.0.AM3
> Environment: Devstudio 10.4.0.AM3-v20170406-1058-B390 (installed form jar installer)
> Reporter: Lukáš Valach
> Priority: Minor
> Fix For: 11.0.0.AM1
>
> Attachments: Spring_in_New_wizard_2017-04-11_10-52-33.png
>
>
> I noticed that after installation of "Spring IDE" from Red Hat Central -> Software/Update there are two folders named "Spring" in "New" wizard dialog (File -> New -> Other...).
> !Spring_in_New_wizard_2017-04-11_10-52-33.png|thumbnail!
> I think that these folders should be merged into one folder.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23861) CDI support is not enabled automatically with JBoss AS 7.1 runtime
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23861?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23861:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> CDI support is not enabled automatically with JBoss AS 7.1 runtime
> ------------------------------------------------------------------
>
> Key: JBIDE-23861
> URL: https://issues.jboss.org/browse/JBIDE-23861
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.4.3.AM2
> Environment: Devstudio AM2-v20170127-1155-B6970, Java 1.8.0_111-b15, JBoss AS 7.1.1.Final
> Reporter: Lukáš Valach
> Priority: Minor
> Fix For: 4.5.0.AM1
>
> Attachments: CdiSupport1.png, CdiSupport2.png
>
>
> When I create a Dynamic Web Project or EJB Project the CDI support should be enabled automatically. It works properly when I have JBoss EAP 7 or Wildfly 10 as target platform, but it doesn't work with JBoss AS 7.1.
> There is no error in the log, there is only warning in the problems view.
> ??JBoss Tools Knowledge Base probelm: Nature/Builder is not installed on project. Use quick fix to enable %KB_REQUIRED_FOR_FACET and Faceted (test environment only) Content Assistant and Validation.??
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24116) NullPointerException in JSFPromptingProvider.getVariables
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24116?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24116:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.4.4.Final)
> NullPointerException in JSFPromptingProvider.getVariables
> ---------------------------------------------------------
>
> Key: JBIDE-24116
> URL: https://issues.jboss.org/browse/JBIDE-24116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Reporter: Automated Error Reporting Bot
> Fix For: 4.5.0.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message:
> java.lang.NullPointerException: null
> at org.jboss.tools.jsf.model.pv.JSFPromptingProvider.getVariables(JSFPromptingProvider.java:268)
> at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:144)
> at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:103)
> at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:83)
> at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:466)
> at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:282)
> at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolve(AbstractELCompletionEngine.java:165)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validate(ELValidator.java:278)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259)
> at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269)
> at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321)
> at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.2.v20161113-1700 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.700.v201604272318 |
> | org.jboss.tools.common.el.core | 3.7.1.Final-v20160408-2358-B112 | 3.8.3.v20161213-1258 |
> | org.jboss.tools.common.text.xml | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160607-2053 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.3.v20161213-1258 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.3.v20161214-1452 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.3.v20161214-1634 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160628-0959 |
> Operating Systems:
> | Linux | 4.7.10.fc23 | 4.8.8.fc24 |
> | MacOSX | 10.11.6 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/574e5d77e4b06056d20... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20529:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> Master JIRA for XML Validation Problems
> ---------------------------------------
>
> Key: JBIDE-20529
> URL: https://issues.jboss.org/browse/JBIDE-20529
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples, server
> Reporter: Rob Stryker
> Assignee: Andre Dietisheim
> Labels: xtriage
> Fix For: 4.5.0.AM1
>
>
> This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months