Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of Adrian.Skehill@iona.com
 designates 65.223.216.181 as permitted sender)
Message-ID: <4541E876.3010300@iona.com>
Date: Fri, 27 Oct 2006 12:07:34 +0100
From: Adrian Skehill <adrian.skehill@iona.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: cxf-dev@incubator.apache.org
CC: stp-dev@eclipse.org
Subject: Re: Apache CXF Integration with the Eclipse STP
References: <453E30F3.3030202@iona.com> <4540B834.5020003@envoisolutions.com>
In-Reply-To: <4540B834.5020003@envoisolutions.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Dan,

eclipse usually manages its dependencies in the form of eclipse plugins, 
instead of jars. So what we're proposing is here is that all the jars 
required by the STP are present and encapsulated in one plugin that we 
can place a dependency on. I've put the exact list of jars that we need 
into the jira issue that I've raised for this task:

https://issues.apache.org/jira/browse/CXF-187

Hope this answers your question.

Adrian.

Dan Diephouse wrote:
> Hi Adrian,
> 
> I think this sounds reasonable. Far be it from me to hinder anyone who 
> is writing an Eclipse plugin which uses CXF! :-)
> 
> One question though: How does depending on CXF differ from depending on 
> a plugin that CXF produces?
> 
> - Dan
> 
> Adrian Skehill wrote:
> 
>> Hi There,
>>
>> As part of the ongoing work within the Eclipse SOA Tools Platform 
>> (STP) project, we are planning on migrating our Service Creation 
>> component to use CXF instead of Celtix 1.0. What we did for Celtix was 
>> to commit all the required jars in order to run the code generation 
>> into the STP CVS repository. The Eclipse Foundation has a very 
>> extensive legal process that needs to be run over all third party 
>> committed components and continuing in this way would take a huge 
>> amount of time and effort, particularly if the jars that CXF depended 
>> on changed. Plus some jars are not re-distributable (e.g. CDDL based 
>> libs) which gives us more problems.
>>
>> So, I would like to propose that instead of updating STP to include 
>> CXF jars, CXF would create an eclipse plugin that the STP could use to 
>> satisfy the dependencies. This plugin would be a very simple wrapper 
>> type plugin, and it would only contain the required libs necessary to 
>> use the CXF generators and any other components that would benefit 
>> from tooling. This plugin would need to be made publicly available for 
>> download and we then in STP would put a dependency to bring it in as 
>> part of our build / test purposes.
>>
>> This should be a fairly straightforward task to do, and we would be 
>> able provide assistance in getting the build system modified to 
>> publish the plugin. Anybody who would download the STP would also need 
>> to bring in this plugin as we will not be able to ship it without 
>> approval from the Eclipse legal department.
>>
>> I'd love to hear back and get the ball moving on this so that then CXF 
>> would be able to benefit from integrating with the STP and Eclipse 
>> environments.
>>
>> Any comments / thoughts / concerns?
>>
>> Regards,
>> Adrian Skehill.
>>
>> Principal Engineer,
>> IONA Technologies.
> 
> 
>