We are evaluating babeldoc for use in a major data integration project. I think we will need to extend it somewhat, since we need to support PGP encryption in pipelines. I loaded the source into our Java IDE and tried to build it, but there are many errors. Should I include every jar in the source distribution in the library path?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, if you need to work with all Babeldoc sources then you should include all libraries. Anyway, there are Ant scripts provided for building Babeldoc without an IDE.
I think someone posted instructions for working with Babeldoc (compiling, debugging) from Eclipse, but that was long time ago. Check mailing lists and/or forums.
Regards,
Dejan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We've done quite a bit of extension work using the Eclipse IDE. The main trick is to run the 'build setupt' and 'build' ant scripts in a cmd prompt first. Once that's done you can use the contents of the build/lib folder in your IDE class path for compiling. Works quite well with auto build in the Eclipse world.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wrote an eclipse HOWTO several months back, which should still be largely valid. I created a babeldoc eclipse project today from a fresh checkout, and it was pretty trivial. Everything I remember from the HOWTO was still valid, and a full build took me about ten minutes, including the checkout. Here is the original message: http://sourceforge.net/mailarchive/message.php?msg_id=6462358
Cheers...
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just noticed that the HOWTO screws up, because it references libraries under the build/ directory rather than the modules/ directory. It's better to use the libraries under the modules/ directory. The build directory won't exist immediately after the checkout.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We use babeldoc for a large multilingual project generating signed certificates in pdf; it works quite well; to compile the source code, use the build.bat and not directly the ant command; in the build.bat; adjust the java_home and classpath variables to your environment (pointing to the correct jdk) and it should work.
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are evaluating babeldoc for use in a major data integration project. I think we will need to extend it somewhat, since we need to support PGP encryption in pipelines. I loaded the source into our Java IDE and tried to build it, but there are many errors. Should I include every jar in the source distribution in the library path?
Well, if you need to work with all Babeldoc sources then you should include all libraries. Anyway, there are Ant scripts provided for building Babeldoc without an IDE.
I think someone posted instructions for working with Babeldoc (compiling, debugging) from Eclipse, but that was long time ago. Check mailing lists and/or forums.
Regards,
Dejan
We've done quite a bit of extension work using the Eclipse IDE. The main trick is to run the 'build setupt' and 'build' ant scripts in a cmd prompt first. Once that's done you can use the contents of the build/lib folder in your IDE class path for compiling. Works quite well with auto build in the Eclipse world.
Thanks for all the great advice. I now have the project loaded in my IDE.
Hi,
I wrote an eclipse HOWTO several months back, which should still be largely valid. I created a babeldoc eclipse project today from a fresh checkout, and it was pretty trivial. Everything I remember from the HOWTO was still valid, and a full build took me about ten minutes, including the checkout. Here is the original message: http://sourceforge.net/mailarchive/message.php?msg_id=6462358
Cheers...
Mike
I just noticed that the HOWTO screws up, because it references libraries under the build/ directory rather than the modules/ directory. It's better to use the libraries under the modules/ directory. The build directory won't exist immediately after the checkout.
We use babeldoc for a large multilingual project generating signed certificates in pdf; it works quite well; to compile the source code, use the build.bat and not directly the ant command; in the build.bat; adjust the java_home and classpath variables to your environment (pointing to the correct jdk) and it should work.
Jan