|
You have to right-click on your project and choose Properties. Then visit the Java Build Path section and click on the Libraries tab. Mark OKogan@xxxxxxxxxxxxxxxxxx Sent by: wdsci-l-bounces@xxxxxxxxxxxx 06/26/2003 01:43 PM Please respond to Websphere Development Studio Client for iSeries To: wdsci-l@xxxxxxxxxxxx cc: Subject: RE: [WDSCI-L] JT400.Jar Mark, Thanks for your help. But I have problem locating 'Add External JAR option' or ' Add Variable option'. Can you tell me where they are or how to define the variable? Thank you Oleg -----Original Message----- From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx] Sent: Thursday, June 26, 2003 11:40 AM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] JT400.Jar Oleg, I believe you always have to do something specific to add it to your projects build path, but there are severals ways to do it. I have used all of these: 1) Define a variable in your preferences that points the folder with your JAR files. In your project, you then use the Add Variable option, select the variable and click Extend to pick the JAR. You could have the variable point directly to your JAR, but since there often related JAR files it is easiest to point to a folder. With this technique, people working in a team need to define the same variable, but it can point to a different location. 2) Create a project called something like Common JARS. And put all of your JARS in it. You can then just check this project in to version control and make sure all of your programmers add it to their workspace. In your other projects, you then just use the Add JAR option and pick them from the resulting list. I like this method because it is easy to update the JARS in a team environment. 3) Just use the Add External JAR option to pull in the JAR from your PC. In this scenario, every developer has to have the JAR in the same location on their PC. As for making it work like VAJ. This company http://www.instantiations.com/ offers a suite of plugins with a lot of nice utilities. Many of them are to make it work more like VAJ. Mark OKogan@xxxxxxxxxxxxxxxxxx Sent by: wdsci-l-bounces@xxxxxxxxxxxx 06/26/2003 12:03 PM Please respond to Websphere Development Studio Client for iSeries To: wdsci-l@xxxxxxxxxxxx cc: Subject: [WDSCI-L] JT400.Jar Hi, All I'm just starting to use WDSC 5.0 and I have a couple of questions. 1) Is there any place where I can import JT400.jar to so every project could use it, or I have to do it every time I create a project. 2) How can I edit 1 method at a time like in VA. Thank you Oleg _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.