richard schmidt wrote:
I was think about about how well maven manages project dependencies and
I suddenly though, could I use it to distribute an application to client
PCs?
Every client PC would have to have maven installed and configured to use
the company repository.
On a shared PC I would install a the application's POM and a batch file
Uses would simply run the batch file, which would run a maven command
that would download the required jars from the company repository and
start up the application.
Of course I would need a plugin to start up the application and I
thought exec-maven-plugin would do the trick. Turns out you need to have
the entire project checked out into the directory, the pom itself is not
enough.
I know that I should be using Webstart, but even with
the webstart-maven-plugin, sometimes webstart is a pain. This is for a
company wide application so we don't need to worry about firewalls,
security, etc.
Is the idea totally crazy?
Not at all. The appassembler plugin was written based on that idea, it
is even still reflected in the code. It was intended that appassembler
creted applications would be able to do a form of self-update, at least
with new SNAPSHOT dependencies. However that part of the plugin/code was
never implemented so it "only" support creating complete bundles of
JARs, but that combined with the deb, rpm, solaris or unix plugins has
made it sufficiently easy to distribute applications for me.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
