Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335407

Summary:	Lifecycle mapping error on parents hard to figure out
Product:	z_Archived	Reporter:	Pascal Rapicault <pascal>
Component:	m2e	Assignee:	Milos Kleint <mkleint>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mkleint
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:	335297, 337220
Bug Blocks:

Description Pascal Rapicault

2011-01-25 20:38:57 EST

When I imported aether (https://github.com/sonatype/sonatype-aether/tree/62df2b8834ee285eae3645be9009927e87456001) each project had an error marker on the build element because of the maven-resources-plugin (it was using 2.3 which is not supported).
When I navigated to the element, the error was reported on the <build> tag which I can understand, but the hardest part in this story was to figure out where to go to fix the issue or at least find the root cause of the issue.
The first thing that would have helped is the ability to have a more detailed message that said that the problem was caused by the element in the pluginManagement of the parents two level from here.
I would have also liked the ability to jump to the problem.

Comment 1 Milos Kleint

2011-01-26 07:38:39 EST

solution shall partly/fully come from implementing #335297

when we have our own custom hover on top of errors (please note that the hover is only possible/practical when there is marker's start/end offset and user has incentive to hover on top of it)

1. hyperlink to the place defined can be part of the hover for sure (not always is the plugin *findable* -think packaging definition)

2. the more detailed message must be provided by the backend (or at least the ui needs precise id of the problem to create the appropriate description)

Comment 2 Milos Kleint

2011-02-08 08:11:35 EST

at the very least the backend has to provide the coordinates/location of the pom file where the definition resides.  

For read-only non-workspace poms line/column coordinate are probably enough, for workspace poms, I'd rather have the location identified by crawling the dom tree document.

Comment 3 Milos Kleint

2011-02-24 04:05:40 EST

http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=a6b6ea7bf2b707688b2449c8cbe45b750f3e7b72


we now have a hyperlink (in xml editor on ctrl-click or on hover, hover also
applicable in form's header popup)

the only outstanding issue is the naming of the hyperlink in xm editor. The
name of the marker needs to be somewhat included in the name (because we can
have multiple ones on same line) but that makes the name long and clumsy.

Comment 4 Pascal Rapicault

2011-02-28 13:51:21 EST

I have used aether as an example again and can see it being fixed.

Comment 5 Denis Roy

2021-04-19 13:25:03 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/