[FELIX-1726] SCR Annotations - Enhance error messages in case of missing project dependencies

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: maven-scr-plugin-1.4.0
• Fix Version/s: maven-scr-plugin-1.4.2
• Component/s: SCR Tooling
• Assignee: Carsten Ziegeler
• Reporter: Stefan Seifert
• Created: 08/Oct/09 23:48
• Updated: 29/Jul/10 10:30
• Resolved: 16/Nov/09 12:22

Description

in rev. 821022 felix removed some dependencies that where unneeded for the code that existed in the scr plugin itself.
there where unneeded to compile the plugin, but they are needed in some usecases for annotation parsing.
e.g. if a project's class is annotated with SCR annotations, and at the same time declares a static field with a slf4j Logger class, reading other static string field values fails with a ClassNotFound exception pointing to a slf4j class.

re-adding the slf4j dependencies again solves the problem.

unfortunately the exception handling in this case is not good - the message is only "Somehing went wrong.", because the ClassNotFound exception was swallowed in ClassUtil.getInitializationExpression method.

Issue Links

• is duplicated by: FELIX-2492 scr plugin: using src annotations causes NoClassDefFoundError and other errors