Editing project libraries without adding to project or module

Hi,

Maybe I'm looking over it, but how can I edit a library without adding it to my project/module?

If I go the module settings I have to click Add to be able to change a library. After making changes I have to use OK, using cancel makes the changes undone. But selecting OK adds the selected library to the module.

I know global libraries can be edited JDK & Global Libraries, but is there an equivelant for project libraries?

TiA

5 comments

You can create it by adding it to a module, and then remove it from the module. That doesn't remove the library from the project, it just leaves it without any references.

Out of curiousity, what's the use case for this. I've never had much use for project libraries at all (I keep a large stable of global libraries), but I really can't imagine the payoff of having one unconnected to a module.

--Dave Griffith

0

Dave,

I know I can remove them again afterwards, but this is strange, not being able to edit a library without adding/removing it...

I have several completely different project with alot modules. I use project libraries for this. I could as well use global libraries, not sure why I choose project libraries :).

About the unconnected, they are all connected to one ore more modules. But then I would first have to go to the module that uses the library I want to edit to be able to edit it. This looks strange and akward. The reason why I edit them is because of new/renamed libraries. If intellij could parse a directory instead of the seperate jar files the problem would also be solved.

Perhaps it would be nicer/better to have a edit project libraries button, like the global libraries.

Alexander

0

Project Libraries are useful when one subscribes to the "Projects Must be Self Contained" philosophy, where ALL dependencies of the project (except build tools like Ant) are included in it's source control checkout such that one can checkout and compile immediately without having to track down and install a hundred required libraries.

0

Completely agreed. But Dave's question was (as I understood it) why
should one create a project library without connecting it to a module.
As long as it isn't connected to a module it isn't used altogether. So
why bother?

Gordon Tyler wrote:

Project Libraries are useful when one subscribes to the "Projects Must be Self Contained" philosophy, where ALL dependencies of the project (except build tools like Ant) are included in it's source control checkout such that one can checkout and compile immediately without having to track down and install a hundred required libraries.


--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0

I was semi-offtopic, replying very specifically to Dave's comment: "I've never had much use for project libraries at all...". I hardly use Global Libraries myself :)

0

Please sign in to leave a comment.