Hey Edison, I don't believe ant is already configured to make a distinction between the nonoss and oss builds. As far as I know that is only in maven.
At the moment I'm just trying to get the regular ant build working again, splitting this off is the next discussion ;-) Cheers, Hugo -----Original Message----- From: Edison Su [mailto:edison...@citrix.com] Sent: Friday, August 31, 2012 10:33 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [DISCUSS] Build process/binaries in our tree/candidate to begin testing with "Ant build-all" works. But it build everything including vmware/kvm, which should be disabled for the apache release? > -----Original Message----- > From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] > Sent: Friday, August 31, 2012 12:11 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: [DISCUSS] Build process/binaries in our tree/candidate to > begin testing with > > Hey All, > > I've push a workaround to master that will take away a bit of the pain > hopefully. > > Change into the deps directory and run 'mvn install'. It will download > all the dependency jars in put them in the deps directory. Most of the > build will be working again, working on the stuff that isn't. > > Cheers, > > Hugo > > -----Original Message----- > From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com] > Sent: Friday, August 31, 2012 8:47 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: [DISCUSS] Build process/binaries in our tree/candidate to > begin testing with > > > -----Original Message----- > > From: Wido den Hollander [mailto:w...@widodh.nl] > > Sent: 31 August 2012 11:17 > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: [DISCUSS] Build process/binaries in our tree/candidate > to > > begin testing with > > > > > > > > On 08/31/2012 08:12 PM, David Nalley wrote: > > > Hi folks: > > > > > > In my haste to get us closer to a presentable source tree - I > > > broke the building of binaries this morning. > > > Essentially I removed all of the jars (and wars) in our source tree. > > > Maven still builds the jars, but ant (and waf) doesn't build > > > binary packages. > > > > > > So we can't carry the jars in the source tree. So we are going to > > > have to fix this at some point prior to release. > > > Maven can deal with this, but it appears maven is only building > jars > > > at the moment, and not touching the rest of the bits that need to > > > happen - or making it easy for deb/rpm. > > > > > > We can revert my deletions (to which I am not necessarily opposed) > > > but it merely means that we have to go through the pain later. > > > So do we want the pain now or the pain later?? > > > > > > > I'd accept the pain now. We need to have this fixed sooner or later. > > > > I'm fetching all the JAR files, putting them on my personal space > > and trying to get deps-ctrl working again. > > > > The binary packaging stuff can call ant prior to building the > packages > > so it fetches all the JAR files we need. > > > > This way the ASF infra won't be hosting any binaries, but our build > > would work. > > I don't mind how we do it, but we absolutely need a complete build > (packages and everything) today so that we can hand that to India for > them to work on while the US is on holiday this Labor Day weekend. > > This could be done by reverting David's changes temporarily and > putting them right back, or whatever, but somehow we need a build that > they can get started on. > > Thanks, > > Ewan.
