[
http://jira.codehaus.org/browse/MFINDBUGS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garvin LeClaire reassigned MFINDBUGS-124:
-----------------------------------------
Assignee: Garvin LeClaire
> Goal that runs findbugs without running compile
> -----------------------------------------------
>
> Key: MFINDBUGS-124
> URL: http://jira.codehaus.org/browse/MFINDBUGS-124
> Project: Maven 2.x FindBugs Plugin
> Issue Type: New Feature
> Reporter: James Roper
> Assignee: Garvin LeClaire
>
> We have a problem with the maven findbugs plugin. We have two modules, an
> API module, and an implementation module that implements the API module. We
> want to run findbugs on both, as a continuous integration build, such that
> the build fails if findbugs fails. But what happens if the API is changed,
> and the implementation is dependent on the API? Running findbugs:check on
> both causes compilation of the second one to fail. mvn package or mvn
> install has to be run on the first one in order for compilation of the second
> one will pass. The solution is to run both mvn install and findbugs:check,
> but findbugs:check always triggers the compile stage again, this is not
> necessary if maven has juts run the install lifecycle. There should be a
> goal for findbugs such that compile doesn't get run first. This can be then
> bound into the lifecycle, and gives users much greater flexibility.
--
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
