Libraries Tab Missing? build 5245

I just started using build 5245. It appears that the "Libraries" tab in the "Modules" setting is missing.

Did this feature move?

7 comments
Comment actions Permalink

Yes, "Libraries", "Dependencies", and "Order" have had all of their functionality merged into the (atrociously named) "Classpath" tab. The information is a lot more compact and understandable, but it's trickier to figure out how to add a new library.

--Dave Griffith

0
Comment actions Permalink

Thanks, Dave. I didn't try editing those libraries. This makes a little more sense now.

0
Comment actions Permalink

Why "atrociously", Dave?
It indeed is the 'classpath' - a well known and well-established notion.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

"Dave Griffith" <dave.griffith@cnn.com> wrote in message news:4051436.1146256524082.JavaMail.itn@is.intellij.net...

Yes, "Libraries", "Dependencies", and "Order" have had all of their functionality merged into the (atrociously named) "Classpath"
tab. The information is a lot more compact and understandable, but it's trickier to figure out how to add a new library.

>

--Dave Griffith



0
Comment actions Permalink

Why "atrociously", Dave?
It indeed is the 'classpath' - a well known and well-established notion.

Because they're more than just "classpath" e.g. javadocs, attached sources, etc.
The term "classpath" suggests just a simple list of Jars that is taken "as it is", without
naming, conditions, dependencies, javadocs, sources, etc.

IMHO in this case it was not a simplification but a try of "oversimplification" :), and in such a
way , that "Libraries Tab" is not intuitive enough anymore (IMHO again :) ).

Ahmed.



0
Comment actions Permalink

It's an excellent switch IMHO. Much better UI, working with it is fast and easy.

0
Comment actions Permalink

I was confused because the new "Classpath" tab looks like the contents of the old "Order / Export" tab.

Once I realized that the "Classpath" tab replaced the "Libraries" tab, everything made sense.

0
Comment actions Permalink

"atrociously" because classpath is one specific implementation of dependency specification, and a limited and fairly hackish one at that. As an implementation technique, it's showing it's age, and likely to be supplanted in the next few years by more general and powerful dependency specification mechanisms (and arguably already has in the case of EARS and WARs).

I will grant that it's well known and well-established naming, and it's also used for the equivalent configuration tab in that IDE named after a moon-shadow, but I would have preferred "Dependencies" for the name of the tab. That's what's being determined there. If my carefully constructed modularization and dependency structures have to be later flattened into a simple linear classpath, that's a limitation of current technologies, not an essential aspect of my project.

Or perhaps I'm just being overly picky.

--Dave Griffith

0

Please sign in to leave a comment.