[
http://jira.codehaus.org/browse/MCLIRR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219418#action_219418
]
Larry Shatzer commented on MCLIRR-28:
-------------------------------------
One thing I forgot to test, running this from the Sonar Clirr plugin. Since the
build has already happened by the time Sonar goes to analyze stuff, the
target/classes directory is already created on the top pom. So it works fine
from the command line when you just run clirr:check, but if Sonar goes to run
the Clirr check, it fails.
So I have also updated my dependency.tree file to be outputted elsewhere, and
adding a build/resource section to include that into the jar file.
I would probably change the summary to better reflect this problem to
"target/classes exists without classes causes plugin to fail" and downgrade the
priority.
> Mutli Module Projects fail on top pom.
> --------------------------------------
>
> Key: MCLIRR-28
> URL: http://jira.codehaus.org/browse/MCLIRR-28
> Project: Maven 2.x Clirr Plugin
> Issue Type: Bug
> Affects Versions: 2.2.2
> Reporter: Larry Shatzer
> Assignee: Simon Brandhof
> Priority: Critical
> Fix For: 2.2.3
>
> Attachments: clirr.patch, MCLIRR-28.zip
>
>
> In multi modules Clirr fails.
> See
> http://archive.codehaus.org/lists/org.codehaus.mojo.user/msg/[email protected]
> Attached is a patch that fixes it.
> If the packaging type is pom, it also is skipped from running.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
