|
|
Re: Scout Book: Can't access the org.scribe plugin in the server [message #1067514 is a reply to message #1067460] |
Tue, 09 July 2013 08:08 |
Urs Beeli Messages: 573 Registered: October 2012 Location: Bern, Switzerland |
Senior Member |
|
|
Thanks, I found a few discrepancies:
My .classpath file was missing these two lines:
<classpathentry exported="true" kind="lib" path="lib/commons-codec-1.8.jar"/>
<classpathentry exported="true" kind="lib" path="lib/scribe-1.3.0.jar"/>
And in my MANIFEST.MF file I had this line
instead of these
Export-Package: org.apache.commons.codec,
org.apache.commons.codec.binary,
org.apache.commons.codec.digest,
org.apache.commons.codec.language,
org.apache.commons.codec.language.bm,
org.apache.commons.codec.net,
org.scribe.builder,
org.scribe.builder.api,
org.scribe.exceptions,
org.scribe.extractors,
org.scribe.model,
org.scribe.oauth,
org.scribe.services,
org.scribe.utils
I've re-read the instructions on how to create that bundle and I believe that I have followed the instructions that were given to a step. What could be the reason that my files look different? Is there something that I could have done differently when adding this library plugin? Or do the modifications that I now made need to be made manually? In which case that should probably be added to the book?
One difference that I noticed was that the second screen of my Library Bundle Wizard (Fig 5.36) looked slightly different in that it has an additional list and two more buttons:
Anyway, now that I've updated my classpath and manifest files the project compiles cleanly. However, accessing the OAuth URL fails because I'm behind an authenticating proxy (but I'll open a separate post for this issue).
Thanks for helping me solve this.
-
Attachment: scribe.png
(Size: 59.82KB, Downloaded 599 times)
|
|
|
Powered by
FUDForum. Page generated in 0.03289 seconds