Changes To Specification Of Libraries In Nika Are A Step Back Follow
I just started working with Nika, setting up a simple project with 3rd party JAR dependencies.
I was dismayed to learn that the ability to specify library or source JARs by selecting all in a single /lib directory was missing. I think that was one of the best changes in IntelliJ 9/10. The new UI has more of a Maven flavor, which I personally don't care for.
If the Maven tie must be stronger, so be it. But I'd like to see the IntelliJ 10 library specification methods remain.
Please sign in to leave a comment.
Are you talking about replacing 'Attach Classes'/'Attach Sources'/... buttons with the single 'Attach Files' item?
In the new UI you still can select one or more jar files or directories in the file chooser. IDEA will automatically add selected jars containing
*.class files as 'class' roots, jars containing *.java files as 'sources' roots and so on. Could you please describe in details what problem do you
have with the new UI?
"Develop with pleasure!"
I've attached a screen shot. I've added the /lib directory containing the .class file for OCR, but as you can see from the screen shot it's still red. If I type "Alt-Enter", IntelliJ asks if I'd like to create the class, not add the import. I'm assuming that it's not finding the JAR.
Of course it could be user error. If you can think of something else that I did wrong I'd appreciate it. Thanks - Duffy
Have you assigned that lib to your module?
IIRC if the name of the lib is grayed out like in your screen shot, then it is not in the dependency list of any module.
Click on Module -> Your Modules -> Dependencies and check. If the library is not in the list click on the "+" button.
I think the real problem is that IDEA no longer asks after creating a library to which module's dependencies it should be added.
On 24.09.2011 06:28, Michael Duffy wrote: