Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: cxf-dev@incubator.apache.org
Subject: Re: split manifest for jdk6 support
Date: Fri, 4 Jan 2008 13:15:32 -0500
User-Agent: KMail/1.9.7
Cc: Jeff Zhang <jeff.zhang@iona.com>
References: <477DCDAF.2070606@iona.com>
In-Reply-To: <477DCDAF.2070606@iona.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200801041315.33053.dkulp@apache.org>


Out of curiosity, why does having that stuff in the manifest cause a 
problem?    The classloaders should, by default, grab the stuff from 
jre/lib first anyway.  Thus, the stuff in the manifest should be 
ignored.

Dan


On Friday 04 January 2008, Jeff Zhang wrote:
> Hi,
>
> I work on CXF jdk6 support. My proposal is split
> cxf-manifest-incubator.jar into 2 manifest jars, one includes all
> javax jars embedded in JDK6, such as jaxws, jaxb, stax, jws,
> annotation, etc..., we can call it cxf-specs-manifest.jar. And another
> one contains the rest jars.
>
> If users use JDK5, they include both manifest jars in classpath, if
> use JDK6, they can only include one manifest. For samples shipped with
> CXF, we can define rule in common_build.xml, it get JDK version from
> OS environment, and put right manifest jar into classpath.
>
> Do you think it reasonable?
>
> Thanks
> Jeff


-- 
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog