You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2013/02/04 15:12:16 UTC
[jira] [Closed] (EMPIREDB-85) Remove declarations of unused
dependencies (from pom.xml)
[ https://issues.apache.org/jira/browse/EMPIREDB-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-85.
---------------------------------
Cleanup of unclosed issues.
> Remove declarations of unused dependencies (from pom.xml)
> ----------------------------------------------------------
>
> Key: EMPIREDB-85
> URL: https://issues.apache.org/jira/browse/EMPIREDB-85
> Project: Empire-DB
> Issue Type: Bug
> Components: CodeGenerator, Core, Struts2 Extensions
> Affects Versions: empire-db-2.0.6-incubating
> Reporter: Marcio Mazza
> Assignee: Francis De Brabandere
> Priority: Trivial
> Fix For: empire-db-2.0.7-incubating
>
> Attachments: empire-db_summary-of-dependency-analyse.txt
>
>
> By running "mvn dependency:analyze"
> one can detect that there are some declared dependencies (in the pom files) which are not used indeed by the codebase.
> Shouldn't they be removed?
> Running against
> http://svn.apache.org/repos/asf/incubator/empire-db/trunk@992776
> e.g., for the CORE we see that commons-collections, mockito and hsqldb were declared but not used at all.
> I see that the mockito dependency comes from the parent, so maybe that should be left alone.
> The output of "mvn dependency:analyze" for the core is, in summary:
> ------------------------------------------------------------------------
> Apache Empire-db Core
> ------------------------------------------------------------------------
> [WARNING] Unused declared dependencies found:
> [WARNING] commons-collections:commons-collections:jar:3.2.1:compile
> [WARNING] org.mockito:mockito-core:jar:1.8.2:test
> [WARNING] hsqldb:hsqldb:jar:1.8.0.10:test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira