Is this change already in master? I tried to do a clean build on master using
mvn clean install -Pdeveloper,systemvm -Dnoredist But then deploying a vmware zone failed with the following error: 2013-11-05 16:25:36,056 WARN [c.c.a.ApiServer] (1039076426@qtp-184764793-9:ctx-de0a2b48 ctx-4f586e61) Unknown API command: addVmwareDc What did I miss here? Thanks -min On 11/5/13 9:03 AM, "Will Stevens" <wstev...@cloudops.com> wrote: >Did this get documented anywhere? It seems that the core build as well as >the nonoss build got changed. I am having trouble locating the beans >now... > >Thanks, > >Will > > >On Tue, Sep 3, 2013 at 11:15 PM, Rajesh Battala ><rajesh.batt...@citrix.com>wrote: > >> +1. >> Sounds great and logical. >> >> On mvn cmd line instead of -Dnonoss we should be using -Dnoredist right! >> >> Thanks >> Rajesh Battala >> >> -----Original Message----- >> From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] >> Sent: Monday, September 2, 2013 5:56 PM >> To: dev@cloudstack.apache.org >> Subject: [DISCUSS] rename nonoss to noredist >> >> Hey, >> >> Does anybody mind if I rename all mentions (that I can find) of "nonoss" >> to "noredist". This will actually reflect what is in the "nonoss" >>build, it >> has nothing to do with opensource, but all with redistribution of binary >> jar packages. Also i noticed that it is currently being "abused" to >>enable >> certain features in the maven build, which is something we should not >>do at >> all. It should just be a convenience setting to enable all profiles that >> depend on non-redistributable binary jar files. >> >> Cheers, >> >> Hugo >>
