qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Vinoski <vino...@iona.com>
Subject Re: Qpid Java Build Instructions - Trunk (M2+)
Date Sat, 02 Dec 2006 18:33:36 GMT
On Dec 1, 2006, at 5:30 PM, Robert Greig wrote:

> On 01/12/06, Steve Vinoski <vinoski@iona.com> wrote:
>> Hi Gordon, I guess the issue here is that qpid-run is specifically
>> intended to work within the layout of the installed package
>> environment. We could
>> 1. Write a new script to be used within your svn working copy,
>> perhaps boiling the common parts of it and the qpid-run script into a
>> separate file that each of them source so as to prevent scripting
>> duplication.
>> 2. Augment qpid-run so that it can also run within the svn working  
>> copy.
>> For users, IMO the first approach would be cleaner. Any other
>> opinions or ideas? I've filed QPID-150 for this, so either post your
>> opinions here or attach them to that issue (or both).
> I wondered if there was a maven artifact that could generate a script
> that just set up the classpath? i.e it would set up an environment
> variable that referenced the relevant jars in your maven repository,
> that you could then source in the qpid-run script.

I don't think there's any need to generate such a script -- maybe we  
should just create a bin directory at the java top level and add a  
script there like the one you're describing?


View raw message