[MPLUGIN-270] Deprecation of classical Maven objects as components is broken when using Javadoc tags

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3
• Fix Version/s: 3.4
• Component/s: maven-plugin-tools-java
• Assignee: Dennis Lundberg
• Reporter: Dennis Lundberg
• Created: 16/Jul/14 07:26
• Updated: 08/Apr/15 08:02
• Resolved: 16/Jul/14 08:53

Description

The fix for MPLUGIN-257 is incorrect for mojos that use Javadoc tags. There are two problems:

• The current code never prints out the warning message, because that part of the code is never reached
• If it had been reached, the type of the parameter would be set to a text, i.e. "${project}" instead of a Java type "org.apache.maven.project.MavenProject"

Issue Links

• is related to: MPLUGIN-257 deprecate classical Maven objects as components