> A bit late now for additional functionaility?
nah...phoenix hasn't entered beta yet...
> If jakarta-avalon-phoenix-bin.jar (which does not yet exist) were
> executable, it could
>
> 1a) extract itself to jakarta-avalon-phoenix-bin (in the current) dir
> 1b) extract itself to a -d specified parameter
> 2) if -f (force) were specified, could overwrite the contents of
> that dir instead of issue an
> error
>
> I know this only saves one use of "jar -xf
> jakarta-avalon-phoenix-bin.jar" after a mkdir, but it
> would be quite neat. Especially when re-used by projects that
> are Avalon dependant, to ship
> avalon/phoenix with one or more sar files pre-installed. Yes, I
> know the idea is to drop sars
> into the apps dir of a pre-installed Avalon, but until Avalon
> gets the recognition that say Ant
> and Tomcat have, it's going to be a hard time convincing people
> that they need to download two
> things to test a fancy product (as well as a convoluted instruction list).
While this approach is possible, I'm not quite sure what
the advantages are. As I see it, apps built on phoenix
should provide two versions, where one contains .jar files
for the ./lib dir and .sar files for in the ./bin dir of
a pre-installed phoenix, and the other one is a snapshot
of phoenix with the correct files already in the lib and
build dirs.
When you talk about source distros, you could do this by
having a dist, a dist-complete (including phoenix), a
dist-src and a dist-src-complete (including binary
phoenix).
Upgrading here is the responsibility of the sysadmin, who
can drop in updated Avalon jars into the phoenix installation
as indicated in your documentation.
In other words, I do not think that it is a good idea to
mix roles here - exactly how other apps include avalon
in their distros is not in the avalon problem space.
> To take it one stage further.. the installer (after installation)
> could invoke engine.Main to
> kickoff Avalon-phoenix. To goal being that the jar would be
> double click installable/runnable for
> the armchair heros of this world.
>
> Anyway, I have half written it (a clone of Main), but figure it
that isn't correct behaviour anymore. The class you're talking
about should implement org.apache.avalon.framework.atlantis.Embeddor,
and possibly extend the provided PhoenixEmbeddor.
> may be unpopular, so am seeking
> opinion.
I have doubts about this proposal; the only advantages sees to
be a 30sec or so speed gain for people that need to install an
app based on phoenix but who do not have phoenix on their
system yet. That's not enough for me to start mixing concerns.
cheers!
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
