Bug 256892 - Allow Viewing of Parent Pom
Summary: Allow Viewing of Parent Pom
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: IAM (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: noteworthy
Depends on:
Blocks:
 
Reported: 2008-11-28 08:11 EST by Allan CLA
Modified: 2012-01-05 13:10 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Allan CLA 2008-11-28 08:11:03 EST 
View the parent pom within eclipse.
Comment 1 Allan CLA 2008-12-02 00:48:12 EST 
Fixed in 20569
Comment 2 Abel Muiño CLA 2008-12-02 02:23:38 EST 
Marking as noteworthy for easier tracking and inclusion in new&noteworthy documents.
Comment 3 Carlos Sanchez CLA 2009-05-06 23:05:00 EDT 
Bug fix released in Q4E version 0.9.0 [0.9.0-Q4E]
Comment 4 Korina Cordero CLA 2009-06-04 07:21:03 EDT 
This fails when the project structure is follows:  Parent project has child project A, child project B and child project C.  C is a child project of B, B is a child project of A.

Stack trace:

Unhandled event loop exception
 
java.lang.NullPointerException
at org.eclipse.iam.pomeditor.MavenProjectHelper.resolveParentModelInReactor(MavenProjectHelper.java:77)
at org.eclipse.iam.pomeditor.pages.AbstractMavenPomPage$MavenContributionItem$1.widgetSelected(AbstractMavenPomPage.java:119)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

This was discovered when we imported Apache Archiva.
Comment 5 Abel Muiño CLA 2009-06-04 09:03:30 EDT 
Since comment #4 is an issue with an existing feature, I have created Bug 279094.

Please clarify on the new bugzilla report in which project does the feature fail (I'm guessing it is project C).
Comment 6 Carlos Sanchez CLA 2010-01-19 14:31:54 EST 
close resolved bugs