You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2007/01/27 19:36:49 UTC
[jira] Updated: (CONFIGURATION-217) Possible Maven2 POM dependency
clash for Servlet-API
[ https://issues.apache.org/jira/browse/CONFIGURATION-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger updated CONFIGURATION-217:
---------------------------------------
Fix Version/s: (was: Nightly Builds)
1.3
> Possible Maven2 POM dependency clash for Servlet-API
> ----------------------------------------------------
>
> Key: CONFIGURATION-217
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-217
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Maven 2.0.4
> Windows XP
> Reporter: Christoph Cenowa
> Priority: Minor
> Fix For: 1.3
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org