Return-Path: 
 <cxf-dev-return-1013-apmail-incubator-cxf-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org
Received: (qmail 70125 invoked from network); 19 Oct 2006 14:13:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Oct 2006 14:13:08 -0000
Received: (qmail 18518 invoked by uid 500); 19 Oct 2006 14:13:08 -0000
Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org
Received: (qmail 18482 invoked by uid 500); 19 Oct 2006 14:13:07 -0000
Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cxf-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cxf-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cxf-dev@incubator.apache.org>
List-Id: <cxf-dev.incubator.apache.org>
Reply-To: cxf-dev@incubator.apache.org
Delivered-To: mailing list cxf-dev@incubator.apache.org
Received: (qmail 18473 invoked by uid 99); 19 Oct 2006 14:13:07 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Oct 2006 07:13:07 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of Daniel.Kulp@iona.com designates
 65.223.216.181 as permitted sender)
Received: from [65.223.216.181] (HELO amereast-smg1.iona.com) (65.223.216.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Oct 2006 07:13:05 -0700
Received: from amereast-ems2.IONAGLOBAL.COM ([10.65.6.84])
	by amereast-smg1.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
 k9JECLW7013571
	for <cxf-dev@incubator.apache.org>; Thu, 19 Oct 2006 10:12:43 -0400 (EDT)
Received: from dilbert.boston.amer.iona.com ([10.65.4.111]) by
 amereast-ems2.IONAGLOBAL.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 19 Oct 2006 10:12:37 -0400
From: Daniel Kulp <daniel.kulp@iona.com>
To: cxf-dev@incubator.apache.org
Subject: Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Date: Thu, 19 Oct 2006 10:12:37 -0400
User-Agent: KMail/1.9.5
References: <4536D166.8050902@iona.com> <4536D1C0.10603@envoisolutions.com>
In-Reply-To: <4536D1C0.10603@envoisolutions.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610191012.37432.daniel.kulp@iona.com>
X-OriginalArrivalTime: 19 Oct 2006 14:12:37.0890 (UTC)
 FILETIME=[A1990620:01C6F388]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On Wednesday October 18 2006 9:15 pm, Dan Diephouse wrote:
> Bozhong Lin wrote:
> > Does anyone has any idea why we have both jsr173-api-1.0.jar and
> > stax_api-1.0.jar? They seem to contain the same set of binary
> > classes, which all belong to Stax api classes.
> Probably errors in dependency's poms. Some include stax-api, some
> include jsr173. I suppose the later is more correct, but the former has
> been around long (then maven people didn't add jsr173 until later).
> Also, the stax API's current version is 1.0.1 so we might want to think
> about using that, however probably not critical ifit involves a lot of
> POM changes.

Just FYI: changing version numbers should NEVER involve a "lot of POM 
changes."    There is a dependencyManagement section of the top level pom 
that should define all the versions of the "stuff" that is depended on by 
all the other artifacts.    In ALL the other poms, the <version> tag 
should be left out of all dependencies so the version in the top level 
pom is picked up.    Thus, it's "easy" to update the entire tree.

Enjoy!
-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194   F:781-902-8001
daniel.kulp@iona.com