Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

2017-11-04 Thread Wido den Hollander
Wido > > Regards. > > > From: Rohit Yadav > Sent: Wednesday, November 1, 2017 12:08:59 PM > To: d...@cloudstack.apache.org; users@cloudstack.apache.org > Subject: Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack > > All

Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

2017-11-04 Thread Rohit Yadav
@cloudstack.apache.org Subject: Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack All, The PR has received enough reviews and (regression) testings to consider it for merging. I'll keep the PR open for few days to receive further reviews and additional testing. Thanks. Re

Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

2017-10-31 Thread Rohit Yadav
55 PM To: d...@cloudstack.apache.org; users@cloudstack.apache.org Subject: Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack All, The fatjar PR that aims at migrating to embedded Jetty is ready for review now: https://github.com/apache/cloudstack/pull/2226 New configuration file up

Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

2017-10-30 Thread Rohit Yadav
` - Remove unmaintained distro packagings and config files Regards. From: Rohit Yadav Sent: Thursday, August 24, 2017 1:24:06 AM To: Syed Ahmed; d...@cloudstack.apache.org Cc: Cloudstack Users List Subject: Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

2017-08-23 Thread Rohit Yadav
rg Cc: Rohit Yadav; Cloudstack Users List Subject: Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack I have always been a big fan of fat, dependency-free binaries. Good work guys! rohit.ya...@shapeblue.comĀ  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue

Re: [DISCUSS] Moving to embedded Jetty and fatjar CloudStack

2017-08-10 Thread Wido den Hollander
> Op 10 augustus 2017 om 14:09 schreef Rohit Yadav : > > > All, > > > Distro provided tomcat6/7/* has caused production issues for few users in the > past. Due to this, the ACS deployments are inconsistent with the version/jars > of tomcat in use. By allowing exploded war to be shipped, can