Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4533D10E.5070503@envoisolutions.com>
Date: Mon, 16 Oct 2006 14:35:58 -0400
From: Dan Diephouse <dan@envoisolutions.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cxf-dev@incubator.apache.org
Subject: Re: Distribution Thoughts
References: <4533BCA7.7040402@envoisolutions.com>
 <200610161339.46188.daniel.kulp@iona.com>
 <4533C9D5.5010001@envoisolutions.com>
 <200610161424.12050.daniel.kulp@iona.com>
In-Reply-To: <200610161424.12050.daniel.kulp@iona.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Daniel Kulp wrote:

>Dan,
>
>  
>
>>>>    * Instead of having cxf-*.jar in lib, I think they should be in
>>>>some other directory like "cxf-individual-modules/" so people don't
>>>>include both the bundled jar and the individual modules.
>>>>        
>>>>
>>>Can you get maven to generate the cxf-incubator manifest jar that
>>>points to jars in another directory?   If so, I'm OK.   At the time
>>>we set this up, that was all we could get it to do.
>>>      
>>>
>>Maybe there is some confusion here because I just noticed that the
>>cxf-incubator.jar is only 9K. IMO this should be a bundle of ALL the
>>CXF modules so people only have to use one jar if they want. So I don't
>>see what the manifest has to do with it...
>>    
>>
>
>The manifest has a CLASSPATH entry in it that points to all the other 
>files.   That's why it's small.    There is no need to re-package all the 
>jars into one jar.    You use the CLASSPATH in the jar to point to all 
>the other jars.      It acts like "one jar" (just need the one jar on the 
>classpath") but keeps the modules separate.
>
>Repackaging will really break things.   A bunch of jars have the 
>META-INF/extensions.xml and META-INF/bus-extensions.xml and other files.   
>
>  
>
Well this should fixed. I'm -1 on doing a final release (not 
necessariliy M1) which doesn't have a bundled jar. Users go nuts when 
you don't have it and they have to use a gazillion jars.

>  
>
>>>>* Do we have
>>>>to distribute activemq?
>>>>        
>>>>
>>>For the JMS examples to work "out of the box", yes.   That said, if
>>>the readme had instructions for obtaining ActiveMQ, I'd be OK as
>>>well.
>>>      
>>>
>>Shouldn't the examples work with just the jars? I don't see any reason
>>why we need a complete copy of the activemq-3.2. We should just be able
>>to use the in memory broker. It would be nice to have the activemq
>>specific jars in an activemq directory/ as it really clutters our
>>dependency list.
>>    
>>
>
>It is just the jars, isn't it?    There are a few config files (to 
>configure activemq to use the correct broker and queues and such) in 
>lib/activemq, but not much else.
>
>  
>

I thought I saw start/stop scripts as well...

- Dan

-- 
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com