application_java deployment updates (ATTN anyone out there who uses it!)


#1

Does anyone else use application_java?

Right now it uses a hack deploy that places things in a folder that
somewhat (but not quite) resembles what the deploy provider would create.

I put in COOK-2523 http://tickets.opscode.com/browse/COOK-2523 which will
convert it over to actually use the deploy provider and do it right.

Plus:

  • deployments using application_java will look just like those from
    app_php, app_python, etc
  • you can deploy from git (with either binaries or an extracted war stored
    on git)

Minus:

  • anything that uses the old method will stop working because the files
    will get placed in a slightly different location (the current version will
    be inside “current” for example)

What are people’s thoughts? Please respond here or on the ticket, i’ve had
trouble finding anyone else who uses it :slight_smile:

Thanks!


#2

I do use it. I had a very quick look through the proposed change and it
looks okay to me.
Sure - I’d have to change things to use it but so what?

On Wed, Mar 13, 2013 at 3:10 PM, Jesse Campbell hikeit@gmail.com wrote:

Does anyone else use application_java?

Right now it uses a hack deploy that places things in a folder that
somewhat (but not quite) resembles what the deploy provider would create.

I put in COOK-2523 http://tickets.opscode.com/browse/COOK-2523 which
will convert it over to actually use the deploy provider and do it right.

Plus:

  • deployments using application_java will look just like those from
    app_php, app_python, etc
  • you can deploy from git (with either binaries or an extracted war stored
    on git)

Minus:

  • anything that uses the old method will stop working because the files
    will get placed in a slightly different location (the current version will
    be inside “current” for example)

What are people’s thoughts? Please respond here or on the ticket, i’ve had
trouble finding anyone else who uses it :slight_smile:

Thanks!