commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Resolved: (CONFIGURATION-217) Possible Maven2 POM dependency clash for Servlet-API
Date Sat, 29 Jul 2006 15:27:14 GMT
     [ ]

Oliver Heger resolved CONFIGURATION-217.

    Fix Version/s: Nightly Builds
       Resolution: Fixed

The dependency was updated to version 2.4 and marked as optional (because it is only needed
by web configurations).

I am in the process of preparing the first release candidate of Commons Configuration 1.3,
so hopefully the next release is close.

> Possible Maven2 POM dependency clash for Servlet-API
> ----------------------------------------------------
>                 Key: CONFIGURATION-217
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>         Environment: Maven 2.0.4
> Windows XP
>            Reporter: Christoph Cenowa
>            Priority: Minor
>             Fix For: Nightly Builds
> As described by ASF bug #33476 Commons Configurations shall depend on Servlet-API 2.4.
The current Maven2 POM of Commons Configuration 1.2 shows a dependency on Servlet-API 2.3.
This is not only a mismatch between Commons Configurations' build configuration and its Maven2
POM but also prevents Maven2 projects from using the Servlet-API 2.4 if also using Commons
Configuration 1.2.
> Could it be possible to fix Commons Configuration 1.2's Maven2 POM to include a dependency
on Servlet-API 2.4, please?
> With best regards, Christoph
> P.S.: My thanks for the quick fix of the Commons Collection dependency problem within
Commons Configuration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message