Re: Placement of external libs/programs

[Peter Donald <pe...@apache.org>]

On Sun, 29 Sep 2002 20:46, Johan Sjöberg wrote:
> What would be the best place for external tools in the Phoenix dir
> structure? Now we have most of the stuff in directories under ./lib.
> mx4j is in the root (./) directory and ./tools is almost empty.
>
> I'm asking because I have been testing the Inno-setup tool that
> Nicola-Ken suggested and I'm trying to get it working nicely with the
> build system.

kool.

> If this tool (or some other similar), or actually the setup compiler
> would be included where should it be put? The same goes for the Wrapper
> if that can be included at some point too.

The way I would like to see it laid out is as follows. 

Any reliable/stable jars/products should not be stored in CVS but are 
downloaded from their download site. MX4J is already downloaded. We should be 
downloading Wrapper and requiring it for our build but no ones got around to 
that yet.

For things that are only used in building the product we should place them in 
tools/ subdirectory. If the jars are part of the server then they should be 
placed in the lib/container directory. If the jars are used by hosted 
applications aswell as the container they should be put in lib/ directory.

XDoclet is in a separate directory altogether as it has been less stable than 
anything else and we need a way to easily upgrade it (Though it looks like 
QDox may be a candidate for replacing xdoclet).

-- 
Cheers,

Peter Donald
-----------------------------------------------
"Only two things are infinite, the universe and 
human stupidity, and I'm not sure about the 
former." -Albert Einstein 
----------------------------------------------- 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Placement of external libs/programs

[Ulrich Mayring <ul...@denic.de>]

Peter Donald wrote:
> On Wed, 2 Oct 2002 21:42, Johan Sjöberg wrote:
> 
>>Anyone using the wrapper on Linux or Solaris with Phoenix? Any good/bad
>>reasons why or why not to include this at the same time as Win32?
> 
> I use it on RH (and derived) linuxen and it works great there.

We're using it on RH Linux (development) and Solaris (production). What 
was the question again? :)

Ulrich

-- 
Ulrich Mayring
DENIC eG, Systementwicklung

Re: Placement of external libs/programs

[Peter Donald <pe...@apache.org>]

On Wed, 2 Oct 2002 21:42, Johan Sjöberg wrote:
> Personally I would like
>
> bin/lib
> bin/lib/native/win32
> bin/lib/native/linux... (could be i386, PPC etc)
> bin/lib/native/solaris

works for me.

> and so on, for cases like this. That would be close to what Leif
> suggested but still not messing up the container's lib dir. And yes, it
> should be just some small conf changes to get it working. I'll try to
> fix myself some time to test this.

kool.

> Anyone using the wrapper on Linux or Solaris with Phoenix? Any good/bad
> reasons why or why not to include this at the same time as Win32?

I use it on RH (and derived) linuxen and it works great there.

-- 
Cheers,

Peter Donald
'Most men would rather die than think. Many do.'
                             Bertrand Russell


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Placement of external libs/programs

[Johan Sjöberg <jo...@avaintec.com>]

Peter Donald wrote:
>
>>OK, the wrapper is part of the server, but not needed by the rest of it.
>>All files are now in ./bin, but as Leif pointed out this is not so clean.
> 
> 
> We could probably move the jars into bin/lib, native files into 
> bin/native/win32/ or bin/native/linux/ or whatever - I presume it is just 
> modifying configuration files to get that going.

Personally I would like

bin/lib
bin/lib/native/win32
bin/lib/native/linux... (could be i386, PPC etc)
bin/lib/native/solaris

and so on, for cases like this. That would be close to what Leif 
suggested but still not messing up the container's lib dir. And yes, it 
should be just some small conf changes to get it working. I'll try to 
fix myself some time to test this.

Anyone using the wrapper on Linux or Solaris with Phoenix? Any good/bad 
reasons why or why not to include this at the same time as Win32?

//
J


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Placement of external libs/programs

[Peter Donald <pe...@apache.org>]

On Tue, 1 Oct 2002 17:18, Johan Sjöberg wrote:
> > Any reliable/stable jars/products should not be stored in CVS but are
> > downloaded from their download site. MX4J is already downloaded. We
> > should be downloading Wrapper and requiring it for our build but no ones
> > got around to that yet.
>
> No prob, just some simple ant tasks for the wrapper.

kool.

> > For things that are only used in building the product we should place
> > them in tools/ subdirectory.
>
> E.g. the setup compiler in this case. There is a small problem though.
> At least with inno-setup. It is distributed as a windows setup EXE so it
> can't be downloaded and extracted. I think that at least the
> command-line compiler, some DLLs and the english language files would
> have to be included in CVS for this to run really smoothly.
>
> OK, I know, if it is installed on _the_ windows build machine its dir
> could be included in ant.properties. BUT, that would make building a
> full dist even more cumbersome than now... this is probably the way to
> start though.

yep.

> > If the jars are part of the server then they should be
> > placed in the lib/container directory. If the jars are used by hosted
> > applications aswell as the container they should be put in lib/
> > directory.
>
> OK, the wrapper is part of the server, but not needed by the rest of it.
> All files are now in ./bin, but as Leif pointed out this is not so clean.

We could probably move the jars into bin/lib, native files into 
bin/native/win32/ or bin/native/linux/ or whatever - I presume it is just 
modifying configuration files to get that going.

-- 
Cheers,

Peter Donald
------------------------------------------------------------
 militant agnostic: i don't know, and you don't know either.
------------------------------------------------------------ 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Placement of external libs/programs

[Johan Sjöberg <jo...@avaintec.com>]

Peter Donald wrote:
>
>>I'm asking because I have been testing the Inno-setup tool that
>>Nicola-Ken suggested and I'm trying to get it working nicely with the
>>build system.
> 
> 
> kool.

It seems to work fairly well, but I have some minor issues with it 
still... I'll get back when it is ready for testing, if at all possible. 
I'm not rushing with this at all, as the whole point with it is to make 
installing and maintaing Phoenix easier. Especially for new people.

>>If this tool (or some other similar), or actually the setup compiler
>>would be included where should it be put? The same goes for the Wrapper
>>if that can be included at some point too.
> 
> 
> The way I would like to see it laid out is as follows. 
> 
> Any reliable/stable jars/products should not be stored in CVS but are 
> downloaded from their download site. MX4J is already downloaded. We should be 
> downloading Wrapper and requiring it for our build but no ones got around to 
> that yet.

No prob, just some simple ant tasks for the wrapper.

> For things that are only used in building the product we should place them in 
> tools/ subdirectory.

E.g. the setup compiler in this case. There is a small problem though. 
At least with inno-setup. It is distributed as a windows setup EXE so it 
can't be downloaded and extracted. I think that at least the 
command-line compiler, some DLLs and the english language files would 
have to be included in CVS for this to run really smoothly.

OK, I know, if it is installed on _the_ windows build machine its dir 
could be included in ant.properties. BUT, that would make building a 
full dist even more cumbersome than now... this is probably the way to 
start though.

> If the jars are part of the server then they should be 
> placed in the lib/container directory. If the jars are used by hosted 
> applications aswell as the container they should be put in lib/ directory.

OK, the wrapper is part of the server, but not needed by the rest of it. 
All files are now in ./bin, but as Leif pointed out this is not so clean.

//
Johan


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>