New plugin WarExec for grails.org

[DavidTinker]

I would like to publish a plugin to grails.org:
https://github.com/davidtinker/war-exec

It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.

My grails.org username is david.tinker.

Usage is simple:

BuildConfig.groovy:
plugins {
    runtime ":war-exec:1.0.0"
    ...
}

$ grails dev war
$ java -jar target/com.brandseye.myapp.war

Thanks
David

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Gert Wohlgemuth]

hi david,

doesn't this do the same?

http://grails.org/plugin/jetty-standalone

Maybe it would be better to combine these plugins to one? I sadly had
not the time in the last year to maintain it.

If this is not desired, feel free to remove my plugin from the repository.

g.


On Thu, Jul 26, 2012 at 7:32 PM, David Tinker <[hidden email]> wrote:

> I would like to publish a plugin to grails.org:
> https://github.com/davidtinker/war-exec
>
> It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.
>
> My grails.org username is david.tinker.
>
> Usage is simple:
>
> BuildConfig.groovy:
> plugins {
>     runtime ":war-exec:1.0.0"
>     ...
> }
>
> $ grails dev war
> $ java -jar target/com.brandseye.myapp.war
>
> Thanks
> David
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
------------------------------------------------------------
Lead Developer - Fiehnlab, UC Davis

gert wohlgemuth

work:
http://fiehnlab.ucdavis.edu/staff/wohlgemuth

phone:
530 665 9477

coding blog:
http://codingandmore.blogspot.com

linkedin:
http://www.linkedin.com/profile/view?id=28611299&trk=tab_pro

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[DavidTinker]

Hi G

I did try your plugin but didn't like the fact that I had to define a
standalone environment and run a separate script to create the
executable war (createStandaloneWar). I wanted to be able to run a war
generated for any environment. Also it seemed to double up the size of
the war.

After I got everything working in a Grails project it was easy enough
to make it into a plugin. My plugin works differently to yours - if I
updated yours to work in the same way people might be unhappy that
their "normal" wars would be executable automatically.

Cheers
David

On Thu, Jul 26, 2012 at 12:44 PM, wohlgemuth <[hidden email]> wrote:

> hi david,
>
> doesn't this do the same?
>
> http://grails.org/plugin/jetty-standalone
>
> Maybe it would be better to combine these plugins to one? I sadly had
> not the time in the last year to maintain it.
>
> If this is not desired, feel free to remove my plugin from the repository.
>
> g.
>
>
> On Thu, Jul 26, 2012 at 7:32 PM, David Tinker <[hidden email]> wrote:
>> I would like to publish a plugin to grails.org:
>> https://github.com/davidtinker/war-exec
>>
>> It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.
>>
>> My grails.org username is david.tinker.
>>
>> Usage is simple:
>>
>> BuildConfig.groovy:
>> plugins {
>>     runtime ":war-exec:1.0.0"
>>     ...
>> }
>>
>> $ grails dev war
>> $ java -jar target/com.brandseye.myapp.war
>>
>> Thanks
>> David
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> ------------------------------------------------------------
> Lead Developer - Fiehnlab, UC Davis
>
> gert wohlgemuth
>
> work:
> http://fiehnlab.ucdavis.edu/staff/wohlgemuth
>
> phone:
> 530 665 9477
>
> coding blog:
> http://codingandmore.blogspot.com
>
> linkedin:
> http://www.linkedin.com/profile/view?id=28611299&trk=tab_pro
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
http://twoogleplus.com/ Online service to cross-post tweets to Google+
http://engage.calibreapps.com/ Engage - Web based goal setting and
performance management

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Gert Wohlgemuth]

Oh ok, was just wondering :)

Sent from my iPhone

On Jul 26, 2012, at 8:07 PM, David Tinker <[hidden email]> wrote:

> Hi G
>
> I did try your plugin but didn't like the fact that I had to define a
> standalone environment and run a separate script to create the
> executable war (createStandaloneWar). I wanted to be able to run a war
> generated for any environment. Also it seemed to double up the size of
> the war.
>
> After I got everything working in a Grails project it was easy enough
> to make it into a plugin. My plugin works differently to yours - if I
> updated yours to work in the same way people might be unhappy that
> their "normal" wars would be executable automatically.
>
> Cheers
> David
>
> On Thu, Jul 26, 2012 at 12:44 PM, wohlgemuth <[hidden email]> wrote:
>> hi david,
>>
>> doesn't this do the same?
>>
>> http://grails.org/plugin/jetty-standalone
>>
>> Maybe it would be better to combine these plugins to one? I sadly had
>> not the time in the last year to maintain it.
>>
>> If this is not desired, feel free to remove my plugin from the repository.
>>
>> g.
>>
>>
>> On Thu, Jul 26, 2012 at 7:32 PM, David Tinker <[hidden email]> wrote:
>>> I would like to publish a plugin to grails.org:
>>> https://github.com/davidtinker/war-exec
>>>
>>> It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.
>>>
>>> My grails.org username is david.tinker.
>>>
>>> Usage is simple:
>>>
>>> BuildConfig.groovy:
>>> plugins {
>>>    runtime ":war-exec:1.0.0"
>>>    ...
>>> }
>>>
>>> $ grails dev war
>>> $ java -jar target/com.brandseye.myapp.war
>>>
>>> Thanks
>>> David
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>>
>>
>> --
>> ------------------------------------------------------------
>> Lead Developer - Fiehnlab, UC Davis
>>
>> gert wohlgemuth
>>
>> work:
>> http://fiehnlab.ucdavis.edu/staff/wohlgemuth
>>
>> phone:
>> 530 665 9477
>>
>> coding blog:
>> http://codingandmore.blogspot.com
>>
>> linkedin:
>> http://www.linkedin.com/profile/view?id=28611299&trk=tab_pro
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> http://twoogleplus.com/ Online service to cross-post tweets to Google+
> http://engage.calibreapps.com/ Engage - Web based goal setting and
> performance management
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Graeme Rocher-4]

Seems to duplicate jetty-standalone

Cheers

On Thu, Jul 26, 2012 at 12:32 PM, David Tinker <[hidden email]> wrote:

> I would like to publish a plugin to grails.org:
> https://github.com/davidtinker/war-exec
>
> It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.
>
> My grails.org username is david.tinker.
>
> Usage is simple:
>
> BuildConfig.groovy:
> plugins {
>     runtime ":war-exec:1.0.0"
>     ...
> }
>
> $ grails dev war
> $ java -jar target/com.brandseye.myapp.war
>
> Thanks
> David
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[DavidTinker]

It works a little differently:

With jetty-standalone you have to run specific script
(createStandaloneWar) to create the war and define a standalone
environment.

My plugin works with any environment and the usual "grails war" script
is used. So all you have to do is depend on this and your wars will be
executable. It also allows environment specific customization of the
Jetty server via Config.groovy.

On Thu, Jul 26, 2012 at 1:18 PM, Graeme Rocher <[hidden email]> wrote:

> Seems to duplicate jetty-standalone
>
> Cheers
>
> On Thu, Jul 26, 2012 at 12:32 PM, David Tinker <[hidden email]> wrote:
>> I would like to publish a plugin to grails.org:
>> https://github.com/davidtinker/war-exec
>>
>> It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.
>>
>> My grails.org username is david.tinker.
>>
>> Usage is simple:
>>
>> BuildConfig.groovy:
>> plugins {
>>     runtime ":war-exec:1.0.0"
>>     ...
>> }
>>
>> $ grails dev war
>> $ java -jar target/com.brandseye.myapp.war
>>
>> Thanks
>> David
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> Graeme Rocher
> Grails Project Lead
> SpringSource - A Division of VMware
> http://www.springsource.com
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
http://twoogleplus.com/ Online service to cross-post tweets to Google+
http://engage.calibreapps.com/ Engage - Web based goal setting and
performance management

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Graeme Rocher-4]

Approved

On Thu, Jul 26, 2012 at 1:30 PM, David Tinker <[hidden email]> wrote:

> It works a little differently:
>
> With jetty-standalone you have to run specific script
> (createStandaloneWar) to create the war and define a standalone
> environment.
>
> My plugin works with any environment and the usual "grails war" script
> is used. So all you have to do is depend on this and your wars will be
> executable. It also allows environment specific customization of the
> Jetty server via Config.groovy.
>
> On Thu, Jul 26, 2012 at 1:18 PM, Graeme Rocher <[hidden email]> wrote:
>> Seems to duplicate jetty-standalone
>>
>> Cheers
>>
>> On Thu, Jul 26, 2012 at 12:32 PM, David Tinker <[hidden email]> wrote:
>>> I would like to publish a plugin to grails.org:
>>> https://github.com/davidtinker/war-exec
>>>
>>> It makes Grails war files executable (java -jar myapp.war) by embedding Jetty.
>>>
>>> My grails.org username is david.tinker.
>>>
>>> Usage is simple:
>>>
>>> BuildConfig.groovy:
>>> plugins {
>>>     runtime ":war-exec:1.0.0"
>>>     ...
>>> }
>>>
>>> $ grails dev war
>>> $ java -jar target/com.brandseye.myapp.war
>>>
>>> Thanks
>>> David
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>     http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>>
>>
>> --
>> Graeme Rocher
>> Grails Project Lead
>> SpringSource - A Division of VMware
>> http://www.springsource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> http://twoogleplus.com/ Online service to cross-post tweets to Google+
> http://engage.calibreapps.com/ Engage - Web based goal setting and
> performance management
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Jeff Brown-3]

On Jul 26, 2012, at 6:30 AM, David Tinker wrote:

> It works a little differently:
>
> With jetty-standalone you have to run specific script
> (createStandaloneWar) to create the war and define a standalone
> environment.
>
> My plugin works with any environment and the usual "grails war" script
> is used. So all you have to do is depend on this and your wars will be
> executable. It also allows environment specific customization of the
> Jetty server via Config.groovy.
>
>

I haven't looked at the details but have you considered tying this together with jetty-standalone so we don't have 2 separate plugins?  I understand that they behave differently but if there is a way to unify them that would be best.

What do you think?



jb

--
Jeff Brown
SpringSource
http://www.springsource.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> After I got everything working in a Grails project it was easy enough
> to make it into a plugin. My plugin works differently to yours - if I
> updated yours to work in the same way people might be unhappy that
> their "normal" wars would be executable automatically.

That could be a setting. To be honest, I'm not sure why we don't have
a single 'standalone' plugin that supports both Tomcat and Jetty.
Feasible?

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Sandro Martini]

Hi all,

>> After I got everything working in a Grails project it was easy enough
>> to make it into a plugin. My plugin works differently to yours - if I
>> updated yours to work in the same way people might be unhappy that
>> their "normal" wars would be executable automatically.
>
> That could be a setting. To be honest, I'm not sure why we don't have
> a single 'standalone' plugin that supports both Tomcat and Jetty.
> Feasible?
>
That would be great, as some Cloud providers like Heroku for example
use jetty-runner to run Grails webapps, see here:
https://devcenter.heroku.com/articles/grails

Bye

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[DavidTinker]

I could do that by adding the "createStandaloneWar" script to war-exec
and this would use a "standalone" environment and port 9090. This
would make war-exec largely backwards compatible with the
jetty-standalone plugin.

On Thu, Jul 26, 2012 at 3:38 PM, Jeff Brown <[hidden email]> wrote:

>
> On Jul 26, 2012, at 6:30 AM, David Tinker wrote:
>
>> It works a little differently:
>>
>> With jetty-standalone you have to run specific script
>> (createStandaloneWar) to create the war and define a standalone
>> environment.
>>
>> My plugin works with any environment and the usual "grails war" script
>> is used. So all you have to do is depend on this and your wars will be
>> executable. It also allows environment specific customization of the
>> Jetty server via Config.groovy.
>>
>>
>
>
> I haven't looked at the details but have you considered tying this together with jetty-standalone so we don't have 2 separate plugins?  I understand that they behave differently but if there is a way to unify them that would be best.
>
> What do you think?
>
>
>
> jb
>
> --
> Jeff Brown
> SpringSource
> http://www.springsource.com/
>
> Autism Strikes 1 in 166
> Find The Cause ~ Find The Cure
> http://www.autismspeaks.org/
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
http://twoogleplus.com/ Online service to cross-post tweets to Google+
http://engage.calibreapps.com/ Engage - Web based goal setting and
performance management

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[DavidTinker]

I would prefer to keep the Tomcat/Jetty plugins separate. People will
choose Tomcat or Jetty and select the appropriate plugin. I don't see
a lot of value in having one plugin that does both. It wil complicate
the code and require extra configuration in applications that want to
use whatever the "non-default" embedded container is.

On Thu, Jul 26, 2012 at 3:44 PM, Peter Ledbrook <[hidden email]> wrote:

>> After I got everything working in a Grails project it was easy enough
>> to make it into a plugin. My plugin works differently to yours - if I
>> updated yours to work in the same way people might be unhappy that
>> their "normal" wars would be executable automatically.
>
> That could be a setting. To be honest, I'm not sure why we don't have
> a single 'standalone' plugin that supports both Tomcat and Jetty.
> Feasible?
>
> Peter
>
> --
> Peter Ledbrook
> Grails Advocate
> SpringSource - A Division of VMware
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--
http://twoogleplus.com/ Online service to cross-post tweets to Google+
http://engage.calibreapps.com/ Engage - Web based goal setting and
performance management

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email