You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/01/04 14:11:12 UTC
[jira] Commented: (MEV-278) Invalid POM for jcoverage 1.0.5 at
iBiblio
[ http://jira.codehaus.org/browse/MEV-278?page=comments#action_54890 ]
Carlos Sanchez commented on MEV-278:
------------------------------------
attached pom is missing log4j and includes itself
> Invalid POM for jcoverage 1.0.5 at iBiblio
> ------------------------------------------
>
> Key: MEV-278
> URL: http://jira.codehaus.org/browse/MEV-278
> Project: Maven Evangelism
> Type: Bug
> Components: Invalid POM
> Reporter: Chris Hagmann
> Attachments: README, jcoverage-1.0.5.pom
>
>
> Jcoverage has a set of dependencies (as taken from its README taken from http://www.jcoverage.org/download/jcoverage-1.0.5-bin.zip):
> THIRD PARTY DEPENDENCIES
> jcoverage is dependant on the following third party libraries, which
> are included in the jcoverage binary distribution.
> bcel 5.1 http://jakarta.apache.org/bcel/
> log4j 1.2.8 http://jakarta.apache.org/log4j/
> getopt 1.0.9 http://gnu.org/
> oro 2.0.7 http://jakarta.apache.org/oro/
> But the POM doesn't state any dependencies, so the transitive dependency resolution mechanism doesn't work.
--
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, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org