August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16471) Implement xterm color selection for ANSI SGR codes 38 and 48

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16471?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16471: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Implement xterm color selection for ANSI SGR codes 38 and 48 > ------------------------------------------------------------ > > Key: JBIDE-16471 > URL: https://issues.jboss.org/browse/JBIDE-16471 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Affects Versions: 4.2.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-17656: -------------------------------------------- I recommend removing System.gc() from setContents()... this seems unnecessary. Closing the File stream should be enough. > Forge crashed Eclipse > --------------------- > > Key: JBIDE-17656 > URL: https://issues.jboss.org/browse/JBIDE-17656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Vineet Reynolds > Fix For: 4.2.0.CR1 > > Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png > > > I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18071) Newly created JPA Entity did not appear in the Project Explorer

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18071?page=com.atlassian.jira.plugi... ] Lincoln Baxter III updated JBIDE-18071: --------------------------------------- Priority: Blocker (was: Major) > Newly created JPA Entity did not appear in the Project Explorer > --------------------------------------------------------------- > > Key: JBIDE-18071 > URL: https://issues.jboss.org/browse/JBIDE-18071 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Following the Ticket Monster example, the {{Event}} JPA entity did not automatically appear in the Project Explorer. It was visible after clicking on 'Refresh' at the package level, though. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17822) Launch shortcut enablement expression caused exception

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17822?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17822: --------------------------------------- [~rrabara], where you able to reproduce the problem ? if so, can you provides me with steps to reproduce ? Thanks > Launch shortcut enablement expression caused exception > ------------------------------------------------------ > > Key: JBIDE-17822 > URL: https://issues.jboss.org/browse/JBIDE-17822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > Attachments: error1, error2, error3, error4, error5 > > > Sometimes when expanding JAX-RS Explorer, a bunch of errors appears in Error Log. > There are 5 similar errors: > {code} > Launch shortcut 'org.testng.eclipse.shortcut' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.testng.eclipse.shortcut.testngSuite' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.jboss.tools.maven.actions.LifeCycleCleanVerify' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.jboss.tools.maven.ui.isCleanVerifyMenuEnabled to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.eclipse.ant.ui.antShortcutWithDialog' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.eclipse.ant.ui.antShortcut' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18137) Update Thym release on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18137?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18137: ----------------------------------- Description: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* YES *Type of dependency:* build *List of bundles added/removed:* TODO was: *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues *License and owner:* Eclipse *Original p2 repo:* http://download.eclipse.org/thym/snapshots *JBoss mirror:* TODO *Sources:* https://github.com/eclipse/thym *Affected projects:* jbosstools-aerogear *Include in JBDS:* YES *Type of dependency:* build *List of bundles added/removed:* TODO > Update Thym release on TP > ------------------------- > > Key: JBIDE-18137 > URL: https://issues.jboss.org/browse/JBIDE-18137 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* TODO -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18072) Error while generating JPA annotations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18072?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18072: ------------------------------ Fix Version/s: 4.2.0.CR1 > Error while generating JPA annotations > -------------------------------------- > > Key: JBIDE-18072 > URL: https://issues.jboss.org/browse/JBIDE-18072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Fix For: 4.2.0.CR1 > > > While following the Ticket Monster example, I got the following error when trying to generate the JPA annotations for the {{Venue}} class (selecting the class in the project explorer, then {{Source>Generate JPA annotations}} : > {code} > java.lang.NullPointerException > at org.hibernate.eclipse.jdt.ui.internal.jpa.common.Utils.findType(Utils.java:73) > at org.hibernate.eclipse.jdt.ui.internal.jpa.common.Utils.findCompilationUnit(Utils.java:51) > at org.hibernate.eclipse.jdt.ui.internal.jpa.common.Utils.findCompilationUnit(Utils.java:90) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActor.updateSelectedItems(JPAMapToolActor.java:273) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActor.updateSelected(JPAMapToolActor.java:109) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActionDelegate.runInternal(JPAMapToolActionDelegate.java:81) > at org.hibernate.eclipse.jdt.ui.internal.jpa.actions.JPAMapToolActionDelegate.run(JPAMapToolActionDelegate.java:56) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:253) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > 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:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18073) Error when triggering content assist on Ticket Monster JPA entity

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18073?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18073: ------------------------------ Fix Version/s: 4.2.0.CR1 > 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 > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18069) Exception occurred in listener of Java element change notification

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18069?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18069: ------------------------------ Fix Version/s: 4.2.0.CR1 > Exception occurred in listener of Java element change notification > ------------------------------------------------------------------ > > Key: JBIDE-18069 > URL: https://issues.jboss.org/browse/JBIDE-18069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Labels: upstream > Fix For: 4.2.0.CR1 > > > Following Ticket Monster example (http://www.jboss.org/ticket-monster/introduction/), I created an {{Event}} entity from Forge wizard. I got the following error in the Log when (or just after) the notification bubble appeared: > {code} > java.lang.NullPointerException > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.compilationUnitResourceExists(AbstractJpaProject.java:1436) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.javaCompilationUnitDeltaIsRelevant(AbstractJpaProject.java:1425) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.javaCompilationUnitDeltaIsRelevant(InternalJpaProjectManager.java:1006) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.handleJavaCompilationUnitDelta(InternalJpaProjectManager.java:998) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.handleJavaDelta(InternalJpaProjectManager.java:933) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.handleJavaElementChangedEvent(InternalJpaProjectManager.java:916) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.javaElementChanged(InternalJpaProjectManager.java:859) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$JavaElementChangeListener.elementChanged(InternalJpaProjectManager.java:1389) > at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1695) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1685) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1537) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1496) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1269) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178) > at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114) > at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:141) > at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105) > at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406) > at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) > {code} > Not sure if it's related to Forge or Eclipse JPA tooling (in which case, it would be an upstream bug, I guess). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18070) New JPA field wizard: content assist for field type is not available

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18070?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18070: ------------------------------ Fix Version/s: 4.2.0.CR1 > New JPA field wizard: content assist for field type is not available > -------------------------------------------------------------------- > > Key: JBIDE-18070 > URL: https://issues.jboss.org/browse/JBIDE-18070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Priority: Minor > Fix For: 4.2.0.CR1 > > > In the "JPA: New Field" wizard, there's a lightbulb before the "Field Type" textfield, which would indicate that content assist is available (which would avoid having to click on the {{Browse...}} button), but nothing appears when doing the Ctrl+space (or Cmd+Space) key. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18071) Newly created JPA Entity did not appear in the Project Explorer

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18071?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-18071: -------------------------------------------- Similarly, new projects are sometimes not imported into the workspace. > Newly created JPA Entity did not appear in the Project Explorer > --------------------------------------------------------------- > > Key: JBIDE-18071 > URL: https://issues.jboss.org/browse/JBIDE-18071 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Following the Ticket Monster example, the {{Event}} JPA entity did not automatically appear in the Project Explorer. It was visible after clicking on 'Refresh' at the package level, though. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 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 August 2014