[
http://jira.codehaus.org/browse/MCLIRR-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann closed MCLIRR-4.
--------------------------------
Assignee: Jochen Wiedmann
Resolution: Fixed
Fix Version/s: 2.1
Fixed with MOJO-723
> Clirr plugin fails if no target/classes directory exist
> -------------------------------------------------------
>
> Key: MCLIRR-4
> URL: http://jira.codehaus.org/browse/MCLIRR-4
> Project: Maven 2.x Clirr Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: N/A
> Reporter: David J. M. Karlsen
> Assignee: Jochen Wiedmann
> Priority: Critical
> Fix For: 2.1
>
>
> I've declared the clirr plugin configuration in the parent pom to avoid to
> declare it in every subproject/artifact.
> Some of these artifacts do not have sources - like a war packaging artifact.
> Clirr should accept that no directory exist - and continue without generating
> a report for the artifact, possibly logging an warning.
> Today the behaviour is:
> [INFO] Comparing to version: 1.0.4
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] basedir C:\myproject\myproject-testwar\target\classes does not exist
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir
> C:\myproject\myproject-testwar\target\classes does not exist
--
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
