Hi guys!

*Thank you very very much, Tilman and Andreas!!*

*Andreas was right!* But the hierarchy in Eclipse is not the same as when
you use separate compilation as in your case.

In Eclipse, the basepath starts at *src. *Suppose that your Eclipse
workspace is called *PDFBox-Workspace*, and that it is somewhere in your
disk, it doesn't matter. Then, suppose that you created a project called
*PDFBox* in this workspace for your PDFBox source code. Then, your
packages/hierarchy starts at:

*PDFBox-Workspace\PDFBox\src*


I debugged and there were two resources missing:

"Identity-H",which is actually in the path:

*PDFBox-Workspace\PDFBox\src*\*org\apache\fontbox\cmap\Identity-H*


and  "sRGB.icc" which is actually in the path:

*PDFBox-Workspace\PDFBox\src\org\apache\pdfbox\resources\cmap*


Eclipse completes the partial paths such as
*org\apache\fontbox\cmap\Identity-H*  with the absolute path:

*C:\...\PDFBox-Workspace\PDFBox\src\*


*But*, when you copy the file to its place in *src* directory, you
should *refresh
*the project on Eclipse "Package Explorer". This will copy the file to:

*C:\...\PDFBox-Workspace\PDFBox\bin*


When your code executes it "wants" things in the *bin *directory not in the
*src*. That is why you should refresh  "Package Explorer". In the case of
Java files, Eclipse compiles the files and copies the class file to *bin*.
But if the file is not a java file it will just copy it there.

Thus, it is possible to compile PDFBox with Eclipse, but the resources must
be put in the way I explained above. Timan, you definitely don't need
maven, 😉

Hope this will help someone!

Thanks again everybody!!

See you next time,

Jack

Reply via email to