[ http://issues.apache.org/jira/browse/GERONIMO-1507?page=all ]
David Jencks updated GERONIMO-1507:
-----------------------------------
Attachment: 1507_offline-deployer.diff
Inspired by this I implemented an offline deployer as part of deployer.jar.
You use the --offline flag. It starts up a kernel in-vm and starts the
configurations listed in var/config/offline-deployer-list and registers a
shutdown hook. Then the normal deploy commands proceed using this in-vm kernel.
I'll apply this when svn comes back to life.
> prototype offline deploy tool
> -----------------------------
>
> Key: GERONIMO-1507
> URL: http://issues.apache.org/jira/browse/GERONIMO-1507
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.1
> Environment: fedora core 2
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
> Geronimo 1.0 branch,
> Reporter: toby cabot
> Assignee: David Jencks
> Priority: Minor
> Attachments: 1507_offline-deployer.diff, offline-patch.txt
>
> Here's a prototype offline deploy tool. It has only one command, for offline
> distribution of applications. It's basically a clone of the online tool so
> it works in a similar way, but for the distribute-offline command it uses a
> hacked version of the packaging plugin's PackageBuilder class to start a
> kernel, load some configurations, and then call the deployer.
> It has one serious bug at the moment: it doesn't switch between tomcat and
> jetty. Not sure why, but I can look into it more.
> It has some missing features:
> - it should get dependencies from somewhere (maybe download them from an
> online Maven repo)
> - it should be able to manipulate config.xml
> - it needs more commands (at least undistribute)
> - it needs to allow the user to specify the config-store to write to
> There's probably a lot of unused code there, too, since I haven't figured out
> what everything does yet. But it's a start.
> You can use it like the online tool. The jar is
> $GERONIMO_HOME/bin/offline.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
