Article View: borland.public.jbuilder.java.api
Article #1874Re: Creating a new library to import into JBuilder
From: Paul Furbacher [TeamB]
Date: Fri, 27 Jul 2001 16:38
Date: Fri, 27 Jul 2001 16:38
72 lines
3570 bytes
3570 bytes
Rhonda Fischer wrote: > I am using JBuilder2 and attempting to create > a library so that I might import it into my code. > > Tools|Project Properties Path Tab: > > Target JDK version: java version "JDK1.1.6_Borland" > Source root directory: > C:\PROJECTS\customer\Interface\ODGUI > Output root directory: > <full pathname where jave .class files are stored> > > I select the 'Library' button and specify details: > > Class path: > c:\newdb\Database\VJDK_WIN; > c:\newdb\Database\VJDK_WIN\com\...\vjdk\classes.zip I just downloaded the Java SDK for Valentina and I find that there is no "classes.zip" in the download. There is a "VJDK.jar" file. If this is what you see, then your _single_ class path description should be c:\newdb\database\VJDK_WIN\VJDK.jar (Why so deep a nested structure "newdb/Database/...?! Why not make it more descriptive: c:/Valetina/....?) > Source path: > c:\valentina\Database\VJDK_WIN\com\...\vjdk There is _no_ source for the Valentina Java SDK, as far as I can tell. Leave that absolutely empty. > Doc path: > c:\customer\docs Huh? Which docs are you thinking about here? This path should point to the JavaDocs for the Valentina SDK. Did you really move them to "c:/customer"? If so, don't do that; keep all components of any SDK you download in the folder hierarchy which the vendor/author placed them. Don't move things around on a whim. If not moved, then enter c:\newdb\database\vjdk_win\docs Although, to get JBuilder 2 to work with the HTML JavaDocs, I think you might have to zip up those docs and point the doc path to that specific zip archive. > [...] as the error msg I receive is "could not create dependency > files" I have checked the dependency file and found a If after setting the paths correctly you still get the dependency error, just try using the library. There was at least one message in the newgroup archives (search engine info -- http://www.borland.com/newsgroups/ngsearch.html) which states that even though you get this message (and I've seen it before with 3rd party libraries -- long ago), you can still effectively use the library in your project. I don't have JBuilder 2 installed, so I can't do any checking on this. One thing you can do is to turn off the "make stable package" flag. That may ease things a bit. Paul Furbacher (TeamB) Please send responses to the newsgroup only. That means, do not send email directly to me. Thank you.
Technical Details
Message-ID:
<3B61991F.256231D2@mac.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!news.maxwell.syr.edu!intgwpad.nntp.telstra.net!news-server.bigpond.net.au!intgwlon.nntp.telstra.net!newsfeeds.ihug.co.nz!ihug.co.nz!dnewsReferences:
<3b61115b_2@dnews>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1089d0,f39bc43818e9b924
X-Google-Attributes: gid1089d0,public
X-Google-ArrivalTime: 2001-07-27 09:56:39 PST
Message-ID: <3B61991F.256231D2@mac.com>
Date: Fri, 27 Jul 2001 12:38:57 -0400
From: "Paul Furbacher [TeamB]" <pfurbacher@mac.com>
Reply-To: pfurbacher@mac.com
Organization: Reverse Alchemy, Inc.
X-Mailer: Mozilla 4.75C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: borland.public.jbuilder.java.api
Subject: Re: Creating a new library to import into JBuilder
References: <3b61115b_2@dnews>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 24.3.167.167
X-Trace: dnews 996251921 24.3.167.167 (27 Jul 2001 09:38:41 -0700)
Lines: 72
Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!news.maxwell.syr.edu!intgwpad.nntp.telstra.net!news-server.bigpond.net.au!intgwlon.nntp.telstra.net!newsfeeds.ihug.co.nz!ihug.co.nz!dnews