Hey Juan Pablo Califano. I took the issues you found and fixed them in the trunk and the bug-branch..
Since you say loud you are new to ant, some lines a side... Only the missed out DEFINE in the doc.xml should have caused problems. Descriptions should not cause problems for the machine but may add confusion to the human. :) Not all targets will be executed running the ant ³production² target. That one only creates production worth deployment files (optimized and debugging off etc). If you run ant without a target the one defined as default of the project (attribute in the first xml tag) should be executed, which is ³production².. So ³ant² and ³ant production² should result in the same thing... Wonder what went wrong the first time. Even though an ant might run with success, each target might have failed building. So you really have to look at the output... I will see what else comes up this week and put up a new tag and zip next week. Thanks a lot for spotting my mistakes!! Niels On 4/7/09 4:42 AM, "Juan Pablo Califano" <[email protected]> wrote: > Sure thing! > > I followed the how-to, downloaded your project and unzipped it. I'm running > Windows XP and had already installed Java 1.6 and Ant (and added to the PATH), > so I was able to run the template build right away. > > First, I must say I'm a total newbie to Ant, so maybe I made some dumb > mistakes. > > Anyway, my first attempt with "ant setup" resulted in an error, but my > internet connection is behaving a bit erratically lately, so probably that > explains it (couldn't catch the exact error). I re ran setup and this time I > got a succesful build. > > Then I ran "ant production" and the build succeded, but when I opened the > index.html, the player complained about an IOError. I traced down the error to > the source code and realized that "Library" had not been compiled. I ran again > "ant" (no args), and then both DefaultFont.swf and Library.swf appeared in the > bin folder, so this time, I opened index.html and everything went fine. > > Reading build.xml, I noticed there were two other targets that hadn't been > built that far: test and doc. I'm not sure wether this is intentional and you > can opt to build them manually if you want or there was some error I didn't > catch. > > In any case, "ant test" passed fine. > > Then I tried "ant doc", but I got some errors back. It complained about > project "macro definition USE-MXMLC" being redefined in USE-TEMP.xml and > DOC.xml. (To be honest, I think I got those errors at this point, but maybe it > was a previous target I tried, not 100% sure). > > I managed to "fix" that changing > > <project name="macro definition MXMLC" basedir="."> > > to > > <project name="macro definition USE-TEMP" basedir="."> > > in build/targets/USE-TEMP.xml > > and > > <project name="macro definition MXMLC" basedir="."> > > to > > <project name="macro definition DOC" basedir="."> > > in build/targets/DOC.xml > > I quoted "fix", because, as I said, I'm not sure if that's the right solution > since I don't have experience with Ant, though it made sense to me and solved > the problem. > > After that, one problem remained with this doc target. It complained about > BUILD::debug not being defined. I've messed up a bit with command line defines > myself so I knew what the problem was. My solution was adding: > > <attribute name="debug" default="true" /> > > and then this > > <arg line='-define+=BUILD::debug,@{debug}' /> > > to DOC.xml, and that solved it, though it seems that hardcoding the debug > value there is probably wrong. > > > Aside from these minor, easy to fix problems, I think you have put together a > great tool, with a lot of potential to ease and improve project managment and > development of AS projects. Congrats! > > I'll look into it more in depth as soon I have some time, since I could use it > (with some tweakings probably) for a medium/large project I'm working on. I'll > have to change / adapt a few things, I think, since my goals and requirements > for this build system are a bit more modest and I already have some of the > issues you're addressing covered by other means (such as svn-external for > managing external libs), but a lot of the macros, targets and templates will > be useful for sure (and cover things that would have taken me a lot to get > working, for sure). > > Again, good work! > > Cheers > Juan Pablo Califano > > 2009/4/6 Niels Wolf <[email protected]> >> Let me know if you find anything missing or not working.. >> >> >> On 4/6/09 5:55 PM, "Juan Pablo Califano" <MailScanner has detected a possible >> fraud attempt from "[email protected]" claiming to be >> [email protected] <http://[email protected]/> > >> wrote: >> >>> Sounds cool, and I think something like this could have been useful in a >>> couple of projects I've been working on. >>> >>> Many times I've made a "mental note" about investigating a bit ANT and >>> non-IDE dependent build systems in general, but never actually did. >>> >>> I'll take a closer look at it as soon as I have more time. >>> >>> Thanks for sharing! >>> >>> Cheers >>> Juan Pablo Califano >>> >>> >>> 2009/4/6, Niels Wolf <MailScanner has detected a possible fraud attempt from >>> "[email protected]" claiming to be [email protected] >>> <http://[email protected]/> >: >>>> Hey. >>>> >>>> Since i can not get it up the wiki.. here just an email... >>>> >>>> Turkish Sweater is.. >>>> >>>> * for medium to bigger Actionscript productions >>>> * collection of ANT macrodefs, targets and templates >>>> * OS independent (used in production on OSX and Windows XP) >>>> * IDE independent (you can run it from your commandline) >>>> * minimal in its dependencies (Java/ANT is needed) >>>> * helping you with third parties Actionscript libraries >>>> * filling the gap between nothing and ANT-Ivy, Maven or similar >>>> >>>> Working with different developers on different OS' and IDEs, frustrating >>>> hours of figuring out which Actionscript library is missing, bloated >>>> repositories with libraries that are already maintained somewhere else, >>>> troubles with setting up an IDE quickly just to make a tiny change and >>>> compile.. ended up in writing this. Now we can checkout any project from >>>> the >>>> repository, run the setup and then production to verify if its formal 'ok'. >>>> >>>> http://code.google.com/p/turkish-sweater/ >>>> >>>> >>>> _______________________________________________ >>>> osflash mailing list >>>> MailScanner has detected a possible fraud attempt from >>>> "[email protected]" claiming to be [email protected] >>>> <http://[email protected]/> >>>> http://osflash.org/mailman/listinfo/osflash_osflash.org >>> >> >> Niels Wolf Niels Wolf -- Niels Wolf Director of Interactive Media MediaCatalyst Herengracht 182 1016 BR Amsterdam The Netherlands t. +31 (0) 20 626 2976 f. +31 (0) 20 626 4026 m. +31 (0) 634 658 783 www.mediacatalyst.com
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
