maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] (MPLUGIN-270) Deprecation of classical Maven objects as components is broken when using Javadoc tags
Date Wed, 16 Jul 2014 13:54:10 GMT

     [ https://jira.codehaus.org/browse/MPLUGIN-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dennis Lundberg closed MPLUGIN-270.
-----------------------------------

    Resolution: Fixed

Fixed in [r1611013|http://svn.apache.org/viewvc?view=revision&revision=1611013].

> Deprecation of classical Maven objects as components is broken when using Javadoc tags
> --------------------------------------------------------------------------------------
>
>                 Key: MPLUGIN-270
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-270
>             Project: Maven Plugin Tools
>          Issue Type: Bug
>          Components: maven-plugin-tools-java
>    Affects Versions: 3.3
>            Reporter: Dennis Lundberg
>            Assignee: Dennis Lundberg
>             Fix For: 3.4
>
>
> 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"



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message