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

Bug 361445

Summary:	Attach the missing ArtifactKey to dependency resolution markers
Product:	z_Archived	Reporter:	Fred Bricon <fbricon>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	dgolovin
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Fred Bricon

2011-10-19 13:58:50 EDT

Build Identifier: 20110916-0149

I need to implement some quick fixes for JBoss Tools (https://issues.jboss.org/browse/JBIDE-9921), for particular missing dependencies (groupId containing org.jboss, version ending with "-redhat").

Currently, my POC IMarkerResolutionGenerator2 implementation must parse the marker's message attribute in order to retrieve the missing dependency infos. (ex. Missing artifact org.apache.commons:commons-lang3:jar:3.0.1-redhat).

Unless I've missed something obvious, I believe it'd be much cleaner if the corresponding ArtifactKey (for example) was added as an attribute to the dependency resolution marker. I'm willing to contribute a patch if that idea makes sense. 

Reproducible: Always

Comment 1 Fred Bricon

2013-05-05 12:12:35 EDT

Added GAVC of missing artifact as different classpath attributes in ArtifactNotFoundProblemInfo.processMarker(IMarker marker)

Fixed with http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=999f32aa09338c34503d9821a7678b5c2e0f4948

Test : https://github.com/tesla/m2e-core-tests/commit/c94d39d24fecde2ad3ea8ba8d6e2825cb73f2ea5

Comment 2 Denis Roy

2021-04-19 13:23:10 EDT

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