Maven as an installation tool

[Eric Kolotyluk <er...@gmail.com>]

Maybe this is too weird, but

Has anyone ever used Maven as an installation tool?

I've been thinking using Maven as a way to install and update software, 
and before I actually go and experiment with the idea I was wondering if 
other people have already thought of this. The idea would be that you 
have a simple bootstrap installer that installs and/or updates Maven 
first. Once Maven is installed/verified, you could then use it to pull 
down the rest of the solution artifacts from the network and then 
integrate them into the end solution. Over time you use the same 
mechanism to assist in software upgrades.

I suspect some people already do something like this for enterprise web 
applications, but I was thinking of something like a desktop application.

Cheers, Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven as an installation tool

["Oliver B. Fischer" <ma...@swe-blog.net>]

Hi,

I build a automated setup for an Webapplication including GlassFish 
configuration, DB setup and configuration and deployment of the 
application itself.

I have choosen Ant as tool for this and I use Maven via the Ant Maven 
Task to handle all dependency related stuff and it works great. The 
solution combines the adavantages of Ant and Maven and turned out to be 
very flexible. But you must know Ant before.

Bye

Oliver


Am 02.03.2012 04:32, schrieb Eric Kolotyluk:
> Maybe this is too weird, but
>
> Has anyone ever used Maven as an installation tool?
>
> I've been thinking using Maven as a way to install and update software,
> and before I actually go and experiment with the idea I was wondering if
> other people have already thought of this. The idea would be that you
> have a simple bootstrap installer that installs and/or updates Maven
> first. Once Maven is installed/verified, you could then use it to pull
> down the rest of the solution artifacts from the network and then
> integrate them into the end solution. Over time you use the same
> mechanism to assist in software upgrades.
>
> I suspect some people already do something like this for enterprise web
> applications, but I was thinking of something like a desktop application.
>
> Cheers, Eric
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven as an installation tool

[Dan Tran <da...@gmail.com>]

Please discard my last comment, wrong topic.

-D

On Fri, Mar 2, 2012 at 12:17 AM, Dan Tran <da...@gmail.com> wrote:
> If i have to repeatedly doing the same thing every day.... maven
> plugin is a way to go since I can run it any where i like as long as
> maven installed and point to our central maven repo.
>
>
> -D
>
> On Thu, Mar 1, 2012 at 11:57 PM, Anders Hammar <an...@hammar.net> wrote:
>>> Sonatype do some black magic for provision developer desktops, check
>>> their website.
>>> There was a demo I saw that pulled down your Eclipse binaries and
>>> installing plugins and did some configuration stuff.
>>> I believe that the bundling of the artifacts for provisioning live in
>>> Nexus - not sure if its a p2 or maven repository.
>>
>> You're referring to their Onboarding solution that they've turned open source:
>> https://github.com/sonatype/onboarding
>>
>> This is for materializing (and update) an Eclipse IDE installation. It
>> pulls artifacts from a P2 repository in Nexus.
>>
>> /Anders
>>
>>>
>>> As the other thread "Is Maven the Answer" says you may be better off
>>> with a pure scripting language or Ant if you want to do non
>>> build-lifecycle event handling.
>>>
>>> Getting Maven to do what you are suggesting is not going to be simply
>>> a matter of hooking assembly plugin together with some dependencies.
>>> You are probably going to have to develop a plugin - at which point
>>> you have to wonder whether it fits into the idea of Maven's lifecycle
>>> (and I suggest not).
>>>
>>> If you are running on Windows tools like SCCM do the installation
>>> management for you.
>>> Is it worth rolling your own?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven as an installation tool

[Dan Tran <da...@gmail.com>]

If i have to repeatedly doing the same thing every day.... maven
plugin is a way to go since I can run it any where i like as long as
maven installed and point to our central maven repo.


-D

On Thu, Mar 1, 2012 at 11:57 PM, Anders Hammar <an...@hammar.net> wrote:
>> Sonatype do some black magic for provision developer desktops, check
>> their website.
>> There was a demo I saw that pulled down your Eclipse binaries and
>> installing plugins and did some configuration stuff.
>> I believe that the bundling of the artifacts for provisioning live in
>> Nexus - not sure if its a p2 or maven repository.
>
> You're referring to their Onboarding solution that they've turned open source:
> https://github.com/sonatype/onboarding
>
> This is for materializing (and update) an Eclipse IDE installation. It
> pulls artifacts from a P2 repository in Nexus.
>
> /Anders
>
>>
>> As the other thread "Is Maven the Answer" says you may be better off
>> with a pure scripting language or Ant if you want to do non
>> build-lifecycle event handling.
>>
>> Getting Maven to do what you are suggesting is not going to be simply
>> a matter of hooking assembly plugin together with some dependencies.
>> You are probably going to have to develop a plugin - at which point
>> you have to wonder whether it fits into the idea of Maven's lifecycle
>> (and I suggest not).
>>
>> If you are running on Windows tools like SCCM do the installation
>> management for you.
>> Is it worth rolling your own?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven as an installation tool

[Anders Hammar <an...@hammar.net>]

> Sonatype do some black magic for provision developer desktops, check
> their website.
> There was a demo I saw that pulled down your Eclipse binaries and
> installing plugins and did some configuration stuff.
> I believe that the bundling of the artifacts for provisioning live in
> Nexus - not sure if its a p2 or maven repository.

You're referring to their Onboarding solution that they've turned open source:
https://github.com/sonatype/onboarding

This is for materializing (and update) an Eclipse IDE installation. It
pulls artifacts from a P2 repository in Nexus.

/Anders

>
> As the other thread "Is Maven the Answer" says you may be better off
> with a pure scripting language or Ant if you want to do non
> build-lifecycle event handling.
>
> Getting Maven to do what you are suggesting is not going to be simply
> a matter of hooking assembly plugin together with some dependencies.
> You are probably going to have to develop a plugin - at which point
> you have to wonder whether it fits into the idea of Maven's lifecycle
> (and I suggest not).
>
> If you are running on Windows tools like SCCM do the installation
> management for you.
> Is it worth rolling your own?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven as an installation tool

[Barrie Treloar <ba...@gmail.com>]

On Fri, Mar 2, 2012 at 2:02 PM, Eric Kolotyluk <er...@gmail.com> wrote:
> Maybe this is too weird, but
>
> Has anyone ever used Maven as an installation tool?
>
> I've been thinking using Maven as a way to install and update software, and
> before I actually go and experiment with the idea I was wondering if other
> people have already thought of this. The idea would be that you have a
> simple bootstrap installer that installs and/or updates Maven first. Once
> Maven is installed/verified, you could then use it to pull down the rest of
> the solution artifacts from the network and then integrate them into the end
> solution. Over time you use the same mechanism to assist in software
> upgrades.
>
> I suspect some people already do something like this for enterprise web
> applications, but I was thinking of something like a desktop application.

Sonatype do some black magic for provision developer desktops, check
their website.
There was a demo I saw that pulled down your Eclipse binaries and
installing plugins and did some configuration stuff.
I believe that the bundling of the artifacts for provisioning live in
Nexus - not sure if its a p2 or maven repository.

As the other thread "Is Maven the Answer" says you may be better off
with a pure scripting language or Ant if you want to do non
build-lifecycle event handling.

Getting Maven to do what you are suggesting is not going to be simply
a matter of hooking assembly plugin together with some dependencies.
You are probably going to have to develop a plugin - at which point
you have to wonder whether it fits into the idea of Maven's lifecycle
(and I suggest not).

If you are running on Windows tools like SCCM do the installation
management for you.
Is it worth rolling your own?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org