This strategy is the wrong way to go about it. Why can't the ZIP file be all-inclusive, and self-documenting? Why can't you design the ZIP to create all needed directory structures by itself? I need the crutch of the mailing list and the main developers or at the very least the application documentation just to BUILD the JAR file? Sorry, this is wrong. At the VERY least you could put a README into the ZIP file that describes the directory structure needed to build the distribution. I shouldn't need the mailing list just to tell me how to build!
With the amazing power and flexibility of Ant, I can't see why you can't support whatever necessary requirements your developers need with CVS directory structures AND create a source distribution that requires nothing more than unzipping the file and running "ant jar" in order to completely build the iText JAR file. Thanks, Christopher Randall On 3/28/06, bruno <[EMAIL PROTECTED]> wrote: > Christopher Randall wrote: > > >I just downloaded the iText 1.4 SRC zip file, and was planning on > >building the jar file from source since the execution environment > >we're running in uses JDK 1.3. > > > >I expected to be able to run "ant jar" and have the resulting JAR file > >immediately available. Apparently, there is an undocumented > >requirement to have a structure two directories up with "www" and > >"src". Haven't had the opportunity to research that would fix it, just > >got really frustrated. A common problem with open source projects is > >assuming all your users are geeky developer types that have a > >pre-configured development environment. I'm a configuration manager > >and don't give a rip about your CVS server environment. I just want to > >BUILD FROM THE SOURCE! > > > >Why do I need to have the simulated CVS environment available to build > >the RELEASED version of the code? I should be able to build without > >any modification WHATSOEVER using Ant and the file structure created > >after unzipping the ZIP file. > > > I create a directory for iText, for instance > $HOME/itext > Then I unzip the src.tar.gz in a subdirectory src: > $HOME/itext/src/ > The following subdirectories appear: > $HOME/itext/src/ant > $HOME/itext/src/com > $HOME/itext/src/META-INF > The main build.xml is also in directory $HOME/itext/src/ > So you can execute ANT after doing cd $HOME/itext/src/ > A new directory will be created: $HOME/itext/build/ > For some ant targets you will also need > $HOME/itext/www/ > This www directory contains resources for building the site > and the tutorial. I think this way of working is standard on > some Linux distributions. Of course, every flavor has its own > 'standard' (I'm thinking about the trouble I had recently to > build iText using Maven). > br, > Bruno > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions
