[ http://jira.codehaus.org/browse/MEV-392?page=all ]
Carlos Sanchez closed MEV-392.
------------------------------
Assignee: Carlos Sanchez
Resolution: Won't Fix
As I said
dependencies have been fixed in the m1 pom, so next versions won't have this
problem
http://svn.apache.org/viewvc/jakarta/commons/proper/logging/trunk/project.xml
We can't change the already deployed version as it will be worst, causing non
reproducible builds
If you want you can ask commons-logging to release 1.1.1 with a fixed pom
> bad dependencies in commons-logging-1.1.pom
> -------------------------------------------
>
> Key: MEV-392
> URL: http://jira.codehaus.org/browse/MEV-392
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Dependencies
> Reporter: Olivier Lamy
> Assigned To: Carlos Sanchez
> Attachments: commons-logging-1.1.pom.patch
>
>
> Hi,
> I have trouble concerning dependencies in commons-logging 1.1
> <dependency>
> <groupId>javax.servlet</groupId>
> <artifactId>servlet-api</artifactId>
> <version>2.3</version>
> </dependency>
> scope must be provided
> <dependency>
> <groupId>avalon-framework</groupId>
> <artifactId>avalon-framework</artifactId>
> <version>4.1.3</version>
> </dependency>
> as 1.0.4 scope must be optionnal
> <dependency>
> <groupId>logkit</groupId>
> <artifactId>logkit</artifactId>
> <version>1.0.1</version>
> </dependency>
> as 1.0.4 scope must be optionnal
--
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
