So, the RPMs build fine for me with the current 4.0 tree, but installing them and trying to use them, it seems something was missed, getting a 500 on the client:
The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application On Thu, Sep 6, 2012 at 9:40 AM, David Nalley <[email protected]> wrote: > On Thu, Sep 6, 2012 at 5:47 AM, Rohit Yadav <[email protected]> wrote: >> >> On 06-Sep-2012, at 3:06 PM, Hugo Trippaers <[email protected]> >> wrote: >> >>> Hey Edison, >>> >>> That should be easy to do once the build is "mavenized". I'm starting to >>> seriously dislike waf already, so would be happy to see it go. >> >> What technical difficulties are you facing with waf? Let's not take decision >> based on one's preference. >> >> If we decide to get rid of war, then I can try to write cmake based >> packaging scripts that package debs and rpm. >> (I package/release debs/rpm for VideoLAN's VLMC, >> https://github.com/bhaisaab/cmakeqt) >> >> Rohit >> > > > So I personally don't see why maven + rpmbuild or maven + dpkg > couldn't be enough for packaging. > Don't we really want people to be able to install CloudStack using > maven? Certainly from a developer standpoint I think that is an end > goal. Aside from the fact that it exists, I don't see anything that > waf currently does that maven can't do. > > --David
