[JBoss JIRA] (JBIDE-18291) Null Pointer Exception when opening HTML5 project's persistence.xml
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-18291:
------------------------------------
Summary: Null Pointer Exception when opening HTML5 project's persistence.xml
Key: JBIDE-18291
URL: https://issues.jboss.org/browse/JBIDE-18291
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Reporter: Jiri Peterka
{code}
java.lang.NullPointerException
at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.getImage(AbstractItemStructuredStateProviderManager.java:158)
at org.eclipse.jpt.common.ui.internal.navigator.NavigatorLabelProvider.getImage(NavigatorLabelProvider.java:65)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.findImage(NavigatorContentServiceLabelProvider.java:197)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getColumnImage(NavigatorContentServiceLabelProvider.java:105)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getImage(NavigatorContentServiceLabelProvider.java:98)
at org.eclipse.ui.internal.navigator.resources.workbench.TabbedPropertySheetTitleProvider.getImage(TabbedPropertySheetTitleProvider.java:65)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.refreshTitleBar(TabbedPropertySheetPage.java:850)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.setInput(TabbedPropertySheetPage.java:754)
at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.selectionChanged(TabbedPropertySheetPage.java:556)
at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:365)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:218)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:122)
at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:112)
at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:80)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:166)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:163)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:160)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:272)
at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:269)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110)
at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:338)
at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:352)
at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36)
at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:126)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1217)
at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:470)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1243)
at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18073) Error when triggering content assist on Ticket Monster JPA entity
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18073?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-18073.
--------------------------------
Not reproducible, closing.
> Error when triggering content assist on Ticket Monster JPA entity
> -----------------------------------------------------------------
>
> Key: JBIDE-18073
> URL: https://issues.jboss.org/browse/JBIDE-18073
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Koen Aers
> Fix For: 4.2.0.CR1
>
>
> The following error occurs when triggering content assist on a JPA annotation attribute of _any_ Entity in the project (after following instructions on http://www.jboss.org/ticket-monster/datapersistence/)
> {code}
> Java Model Exception: Java Model Status [/Users/xcoulon/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.1.Final/hibernate-jpa-2.0-api-1.0.1.Final.jar is not on its project's build path]
> at org.eclipse.jdt.internal.core.PackageFragmentRoot.getRawClasspathEntry(PackageFragmentRoot.java:562)
> at org.eclipse.jdt.internal.core.JavaElement.getJavadocBaseLocation(JavaElement.java:714)
> at org.eclipse.jdt.internal.core.BinaryType.getJavadocContents(BinaryType.java:1011)
> at org.eclipse.jdt.internal.core.BinaryField.getAttachedJavadoc(BinaryField.java:121)
> at org.eclipse.jdt.internal.core.ResolvedBinaryField.getAttachedJavadoc(ResolvedBinaryField.java:1)
> at org.eclipse.jdt.internal.ui.text.javadoc.JavadocContentAccess2.getHTMLContent(JavadocContentAccess2.java:500)
> at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:689)
> at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:607)
> at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:599)
> at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:163)
> at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:129)
> at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:85)
> at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18020) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Forge]
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18020?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-18020.
------------------------------
Verified in JBT 4.2.0.CR1a build.
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Forge]
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18020
> URL: https://issues.jboss.org/browse/JBIDE-18020
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Forge]: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18174) cdi.ui tests failure
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18174?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-18174.
------------------------------------
verified on jenkins. All CDI tests passed.
> cdi.ui tests failure
> --------------------
>
> Key: JBIDE-18174
> URL: https://issues.jboss.org/browse/JBIDE-18174
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> {code}
> Failed tests: testCAELProposalFilteringInXHTML(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testCAELProposalFilteringInJSP(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testEL(org.jboss.tools.cdi.ui.test.CATest): Content Assistant returned no proposals
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18083:
-------------------------------------
OK I see it now. I'm not sure what I had done wrong when testing before but it is very obvious this is occurring. Now, how to fix. :|
> Issues in the new "Edit server runtime environment" window
> ----------------------------------------------------------
>
> Key: JBIDE-18083
> URL: https://issues.jboss.org/browse/JBIDE-18083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu 14.04, Eclipse 64 bit, Java 1.7
> Reporter: Wolfgang Knauf
> Assignee: Daniel Azarov
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
> Attachments: server_runtime.png
>
>
> See attached screenshot: there are three problems in the "Edit Server runtime environment" window.
> a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused
> b) same for the button "Installed JREs"
> c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15518) Support CDI extensions provided without extension service
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15518?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-15518.
------------------------------------
[~scabanovich] Thanks! Closing.
> Support CDI extensions provided without extension service
> ---------------------------------------------------------
>
> Key: JBIDE-15518
> URL: https://issues.jboss.org/browse/JBIDE-15518
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi, cdi-extensions
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> CDI 1.1 specification recommends to register extensions in META-INF/services/javax.enterprise.inject.spi.Extension. However, Weld implementation and Wildfly choose to add extensions directly, without service.
> Now we find only extensions registered in service. We have to add 'hardcoded' extensions as well.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months