Hi Rohit, > mvn -P deps is for the old ant system, for master we've deprecated ant. > That brings us the questions, should we do something about the ant xmls and deprecated code?
My initial thought was that it makes sense to remove the deprecated code. However, so far, the only way I have been able to get a working CloudStack setup using the master branch, Ubuntu and KVM was to hack mvn -P deps to work and then run dpkg-buildpackage (as per description above). Until we have instructions on another method to get an agent running using that configuration, I'd prefer to leave the deprecated options in. Thanks, Dave. On Wed, Nov 7, 2012 at 2:37 PM, Rohit Yadav <[email protected]> wrote: > > On 06-Nov-2012, at 8:36 AM, Dave Cahill <[email protected]> wrote: > > > Hi Edison, > > > > Understood - sounds like .deb package building is not supposed to work on > > master. > > > > Do you know if anyone is working on making .deb building work using maven > > on master? From the first thread you linked [1], it sounded like Noa > Resare > > at Spotify might start working on it, but I don't see any activity after > > that. The wiki mentions this branch in relation to getting debs / maven > > working, but it doesn't seem to have been updated in a month: > > https://github.com/bhaisaab/incubator-cloudstack/tree/debs-maven > > Yes that's my personal branch. I initially proposed and got the debian > packaging working using maven plugin, but it never got through so I stopped > working on that tree. We will be most probably using debian control files > for packaging, as Wido suggested he will take a lead on that as soon as > he's available. > > But, if you need it soon why not please help us fix this; patches welcome! > > > > > If no-one is working on .deb package building, is there an alternative > way > > to keep developing on master with debian / Ubuntu? I can easily run the > > management server from source ("mvn -pl :cloud-client-ui jetty:run"), but > > running the agent from source is a bit messier, as the management server > > needs to SSH into the host and run the agent via the init script ("sudo > > service cloud-agent start"). > > > > I should also mention that by fixing the "mvn -P deps -pl deps" issue I > > mentioned above, I was able to run dpkg-buildpackage successfully, > install > > the resultant .debs successfully on an Ubuntu 12.04 machine, and get a > > basic CloudStack setup (2 guest VMs, basic networking) working that way. > If > > building that way results in .debs which shouldn't work, should we remove > > some of the broken options (e.g. the maven "deps" profile) from master to > > avoid confusion? > > mvn -P deps is for the old ant system, for master we've deprecated ant. > That brings us the questions, should we do something about the ant xmls > and deprecated code? > > Regards. > > > > > Any input appreciated. > > > > Thanks, > > Dave. > > > > > > [1] http://markmail.org/message/lsjigqvnbkjtbl4y > > > > > > > > > > > > > > On Tue, Nov 6, 2012 at 3:59 AM, Edison Su <[email protected]> wrote: > > > >> I don't the deb build on master will work, as we moved build system from > >> ant to maven, the artifacts build by maven is quite different from > >> ant(regarding to the path). You can find the discussion about the build > >> system in the following the mail threads: > >> http://markmail.org/message/lsjigqvnbkjtbl4y > >> http://markmail.org/message/utce4esqjl7xhwr4 > >> > >> -----Original Message----- > >> From: Dave Cahill [mailto:[email protected]] > >> Sent: Monday, November 05, 2012 1:13 AM > >> To: [email protected] > >> Subject: Proposed fixes for debian package building process > >> > >> Hi, > >> > >> There appear to be some errors in the debian package building process; > I'd > >> like to double-check my approach for fixing them. > >> > >> The wiki [1] gives the procedure for building debian packages as: > >> mvn install -P deps && dpkg-buildpackage > >> > >> However, mvn install -P deps fails with: > >> > >> [ERROR] Failed to execute goal on project cloud-deps: Could not resolve > >> dependencies for project > >> org.apache.cloudstack:cloud-deps:jar:4.1.0-SNAPSHOT: Could not find > >> artifact org.apache.cloudstack:cloud-awsapi:jar:4.1.0-SNAPSHOT in > >> apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1] > >> > >> The reason for this failure seems to be this section of deps/pom.xml: > >> <dependency> > >> <groupId>org.apache.cloudstack</groupId> > >> <artifactId>cloud-awsapi</artifactId> > >> <version>${project.version}</version> > >> </dependency> > >> > >> ${project.version} is 4.1.0-SNAPSHOT, however looking at > >> > https://repository.apache.org/content/groups/snapshots/org/apache/cloudstack/cloud-awsapi/ > >> , > >> I only see 4.0.0-SNAPSHOT. > >> > >> If I replace ${project.version} for cloud-awsapi in deps/pom.xml with a > >> hardcoded "4.0.0-SNAPSHOT", mvn -P deps succeeds. An alternative fix > would > >> be if 4.1.0-SNAPSHOT version of cloud-awsapi was available on > >> repository.apache.org. > >> > >> I also found that in order for dpkg-buildpackage to succeed, I needed to > >> run "mvn install -P deps -pl deps" rather than just "mvn install -P > deps". > >> > >> For reference, if you run dpkg-buildpackages without running "mvn -P > >> deps", the error returned is: > >> /PATH/incubator-cloudstack/build/build-aws-api.xml:34: taskdef class > >> org.apache.axis2.tool.ant.AntCodegenTask cannot be found > >> > >> Lastly, I would have expected "mvn clean" to remove the .jars in the > deps > >> folder, however it does not - this made debugging "interesting"! > >> > >> Proposed changes: > >> * Hardcode 4.0.0-SNAPSHOT as the version of cloud-awsapi in > deps/poms.xml > >> * Change the wiki to reflect the fact that "mvn install -P deps -pl > deps" > >> needs to be run when building debian packages > >> * Change mvn clean to remove the jars from the deps folder > >> > >> Please let me know if those changes make sense, or if I'm missing > >> something. If they look OK, I'll create a patch and submit. > >> > >> Thanks, > >> Dave. > >> > >> [1] > >> > >> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+Maven#BuildingwithMaven-BuildingCloudStack > >> > > > > > > > > -- > > Thanks, > > Dave. > > -- Thanks, Dave.
