Global libraries and path variables

Currently in IDEA4 it is not possible to setup global libraries, or any libraries for that matter, using path variables through the GUI. You need to open up the relevant IDEA file and do it manually. This then works for libraries other than globals. This is pretty annoying since these are the very library definitions that I wish to parameterise.
Can you add this please?

10 comments
Comment actions Permalink

Em Wed, 23 Jun 2004 18:23:44 +0400, Saqib escreveu:

Currently in IDEA4 it is not possible to setup global libraries, or any
libraries for that matter, using path variables through the GUI. You need
to open up the relevant IDEA file and do it manually. This then works for
libraries other than globals. This is pretty annoying since these are the
very library definitions that I wish to parameterise. Can you add this
please?


Actually, path variables are automatically used if you add a library
that's under a currently defined path variable.

--
Marcus Brito <pazu@animegaiden.com.br>


0
Comment actions Permalink

OK. But what if a global library is defined and it looks at some std locations for jars. Its these locations that I would like to define with path vars, not the location of the global library. As far as I know, global libraries are kept in the installation or user folder?

0
Comment actions Permalink

I don't really understand you:

As far as I know, global libraries are kept in the
installation or user folder?

The jars itself are whereever you have them. They are referenced in the project (ipr) file.
If you set a path variable to a specific directory then this directory is replaced with the path variable in every references to the directory or any of its sub-directories.
E.g. we have global libraries in something like "H:\dev\ROOT_EXTERN\" - which is "/dev/ROOT_EXTERN" on Linux. So everybody has path variable "ROOT_EXTERN" set to either of these directories depending on wether she works on Windows or Linux. If you have a global library that uses "H:\dev\ROOT_EXTERN\junit\lib\junit381.jar" that path gets stored at "$ROOT_EXTERN/junit/lib/junit381.jar" in the project file, so that the project can be shared via CVS for all platforms.

0
Comment actions Permalink

I agree that this would normally be true. Unfortunately we work with Clearcase snapshots. Because different people in the team are normally working on a number of different views we have these mounted on different drives. Thats why I would like the ability for every developer to define a path variable that maps to the libraries in their environment. With global libraries having the ability to reference path variables and global libraries being able to pick these up, having all developers working off a single set of project files would become that much easier.

0
Comment actions Permalink

They are referenced in the project (ipr) file.
If you set a path variable to a specific directory
then this directory is replaced with the path
variable in every references to the directory or any
of its sub-directories.


I wish it would be the case, but first of all, global libraries are referenced in config/options/applicationLibraries.xml, and unfortunately path variables in this file do not seems to be recognized (if you edit file manually) or put there automatically on library creation. Is this a bug? I would say so. Or maybe I am wrong, and it just me and my weird setup?

0
Comment actions Permalink

I dont think it is just your setup - this does strike me as either a bug or a glaring oversight. I think global libraries in particular ought to be path variable enabled.

0
Comment actions Permalink

On Thu, 24 Jun 2004 01:19:15 +0400, Stephen Kelvin wrote:

The jars itself are whereever you have them.



E.g. we have global libraries in something like "H:\dev\ROOT_EXTERN\" -
which is "/dev/ROOT_EXTERN" on Linux.


That path on Linux really was just an example, right? You're not actually
storing regular files under /dev, are you?

--
Mark Scott

0
Comment actions Permalink

Does this effect anyone else? Also, as part of this request, does anyone think it would be a good idea to have the facility enter a path for the contents directly rather than having to select a path. This would be useful when defining libraries on network drives without having to specify a drive, e.g.
filehost\path\to\file.jar. What do people think?

0
Comment actions Permalink

This is already possible if you edit the ipr file manually like this:

jar://Z:/Repository -> jar:////servername/share/Repository

0
Comment actions Permalink

I agree that it is currently doable but why should you have to edit the project files? Why not have the ability to enter the path manually?

0

Please sign in to leave a comment.