[
http://jira.codehaus.org/browse/MNG-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168645#action_168645
]
Benjamin Bentmann commented on MNG-4075:
----------------------------------------
Hm, would it maybe make sense to distinguish between plugin artifacts and
regular project dependencies here? For the case reported here, the warning is
apparently oversized since the plugin is not actually used in the build. But
for regular dependencies used to setup compile/test class paths I still believe
it's right to inform the user that the class path does not reflect the current
reactor output.
Another/additonal option would be to reduce the warning itself to a single line
and move only the detail output to debug level.
> Tone down warnings about reactor dependencies that don't have an associated
> file
> --------------------------------------------------------------------------------
>
> Key: MNG-4075
> URL: http://jira.codehaus.org/browse/MNG-4075
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.1.0
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1.0
>
>
> currently this is logged to the WARNING level, but it can be disquieting
> without causing any real problems. I'm not entirely sure how these messages
> come up during the clean phase, but at least in the CXF project, they
> definitely seem to.
> We should tone them down to the DEBUG log level for now, unless/until we can
> find a way of being certain they're going to cause a problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
