Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 51695 invoked from network); 26 Jun 2006 19:48:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Jun 2006 19:48:11 -0000 Received: (qmail 42994 invoked by uid 500); 26 Jun 2006 19:48:09 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 42888 invoked by uid 500); 26 Jun 2006 19:48:09 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 42877 invoked by uid 99); 26 Jun 2006 19:48:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2006 12:48:08 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2006 12:48:08 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4B55D410008 for ; Mon, 26 Jun 2006 19:46:32 +0000 (GMT) Message-ID: <24150084.1151351192305.JavaMail.jira@brutus> Date: Mon, 26 Jun 2006 19:46:32 +0000 (GMT+00:00) From: "Oliver Heger (JIRA)" To: commons-dev@jakarta.apache.org Subject: [jira] Commented: (CONFIGURATION-217) Possible Maven2 POM dependency clash for Servlet-API In-Reply-To: <12070155.1151057069859.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/CONFIGURATION-217?page=comments#action_12417890 ] Oliver Heger commented on CONFIGURATION-217: -------------------------------------------- We have discussed this issue on the developers' list with some maven experts. Here is a link to this thread: http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=115117131729595&w=2 Outcome is that once released POMs should not be changed afterwards. I hope that the 1.3 release of Commons Configuration 1.3 won't be too far in future. Then we can update the dependency to Servlet API 2.4. > Possible Maven2 POM dependency clash for Servlet-API > ---------------------------------------------------- > > Key: CONFIGURATION-217 > URL: http://issues.apache.org/jira/browse/CONFIGURATION-217 > Project: Commons Configuration > Type: Bug > Versions: 1.2 Final > Environment: Maven 2.0.4 > Windows XP > Reporter: Christoph Cenowa > Priority: Minor > > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org