From: Michal Č. <mic...@em...> - 2010-01-09 11:20:10
|
Hi Tristan, I think that making one standalone jar file with all the dependencies is definitely a step forward. Its cleaner and it will make it easier to run 2APL from the command line, as previously one also had to ensure that CLASSPATH variable points to the folder with libraries. Automatic generation of timestamped zip file is also nice, but I would make this step a separate ant target (something like "zip-release"). Some people use "ant run" to play with their 2APL platform, which is dependent on the "release" target. If this target also creates a zip file, it slows down the building process and fills up root folder with a zip file for every day a programmer uses "ant run" command. What do you think? Regards, Michal On Thu, Jan 7, 2010 at 7:39 PM, Tristan Behrens <be...@in...>wrote: > Hi all, > > I have played with the ant-file of 2APL a bit. > > Please be so kind and give an experiment of mine a try. It will only take > one minute. Go to the trunk folder and run "ant release". > > After that you will see two things. First, there are no libs in the > release-folder. They are included in the jar-file. Second, the build-file > automatically creates a zip-file. > > What do you think? > > Best > Tristan > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > apapl-developers mailing list > apa...@li... > https://lists.sourceforge.net/lists/listinfo/apapl-developers > |