On Nov 24, 2006, at 11:41 AM, Robert Greig wrote:
On 24/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
Hi Robert, sorry for the delayed response, but it's the Thanksgiving
holiday here.
No problem.
I guess it depends what exactly you're looking for. You may have
already found that if you go into the distribution subdirectory and
run maven, you get tarballs and such. They are still missing javadoc
and would be missing some of the notices and license files and such,
but I think that's OK since you're just building a snapshot. However,
if there are things missing that you definitely need, then tell me
what they are and I'll quickly address them.
The only thing I think is the generation of the *-launch jars, in
particular broker-launch.jar which includes all the classpath info in
the manifest file.
The distribution mvn build already builds one of these -- it's named
qpid-incubating.jar. I think all this requires is fixing the Windows
scripts to use that jar name, right?
--steve
Without these the qpid-server shell script doesn't work, but the
qpid-run script (which creates the classpath by calling out to find)
does work as a workaround on unix platforms.
On Windows though, there is not an obvious workaround since the only
other option (I think) is to type in all the deps into the batch file.
With that I think we should be OK for what the team needs to start
developing.
RG
