--- Andrei <alapitski@rogers.com> wrote:
>
> Now fully opposite question. How to compile java within ilink. My small
> automation program consists of Ilink and ProE portions. It compiles ok
> outside of ilink since I have CLASSPATH env properly set for ilink/proe
> libraries. But when I try to compile within Ilink it is ignoring system
> CLASSPATH and using its own intralink.jar only. So question is how to force
> ilink compiler to use proe libraries?
I assume you're referring to JLink libraries. Yes, you can do this,
in a couple of different ways. Editing the LoginData.properties file
is the easiest.
If you're an administrator, you might find it easier to deploy your
application by adding the JLink jar file(s) to this folder:
<intralinkinstallfolder>\i486_nt\jre\lib\ext
Java automatically knows about and uses any jar files in there. If
other users are going to run your app, it would be easier to add the
jar file there, than edit several LoginData.properties files. This
takes care of compilation and runtime issues.
I don't know about you guys, but I had to use forward slashes on
windows for Intralink to recognize the jar file:
COMPILER_CLASSPATH=<proe_installdir>/text/java/pfcasync.jar;<proe_installdir>/text/java/pfc.jar
That's all on one line. Kind of weird if you ask me.
Marc