Re: Netbeans/Cygwin/JDK issue
Mark Space wrote:
To set the classpath, just add it to the existing CLASSPATH variable.
(For Cygwin, I guess you'd use your example and set CLASSPATH=/c/java)
I'm not sure of your point. The OP gave an example of using /c/java/a
as a classpath. I assumed the extra /a was his issue.
Cygwin drives have the format /cygdrive/c/, not merely /c/. /c/ would map to
%CYGWIN_INSTALL_DIR%/c/, not C:/.
Cygwin also allows the notation c\:/.
Lew wrote:
For that matter, what makes you think the OP is even using Windows?
Mark Space wrote:
If he's running *nix or Solaris or a Mac, why would he need Cygwin? ;-)
You are right. I missed the part of the original message that said:
Can you guide me on cygwin [sic] part?
That's not the only mistake I made in my post, but I have enough ego not to
point out any more.
For me, it's more convenient to set the system CLASSPATH once, and not mess with it again. If you are running more complicated set-ups which require different .jars for different versions of JDK and project, I can see that this would be rather inconvenient and setting the class search path for each project might be better.
I usually work on multiple projects, not all of which use the exact same
libraries. A global CLASSPATH is useless to me.
I see how it would work for other scenarios, though.
My only issue there is that CLASSPATH is extrinsic to the compilation command
and therefore harder by a skootch to track. The -cp option is right there in
the compilation command (or Ant script) where you can't miss it.
A similar argument pertains to putting libs in the shared/ (or equivalent)
library of an application server vs. in the application-specific lib/ folder.
--
Lew