Module libraries not displayed in artifact editor? Follow

Hi.

Can it be this issue: http://youtrack.jetbrains.net/issue/IDEA-26142 ?
One just has to reopen the dialog to see the library.

Alexander.

Unfortunately, no, it does not appear to be this issue.  This does not just happen after a new library is created, and I cannot get the module library to appear in the interface.  I've tried many permutations of actions to make this work.  

I'm attaching screenshots just to clarify.

Here are the relevant module dependencies:


And here's the artifact editor:


Note "SimulationLibs" is missing, and idea doesn't even warn me that it is missing.

Now, here's another piece of information, which may or may not be relevant.  I have a strange project structure, because I was trying to figure out how to organize project / modules.  My project dir is ~/DEV/foo  and my modules are all in ~/DEV/foo-modules.  I'm wondering if this is breaking some assumption about where module info is kept?

Appreciate any help - this is not a roadblock, but is an inconvenient bug.

thx,
josh

Hi Josh,

I was able to reproduce your problem. Corresponding note is added to IDEA-26142.

Here is my use-case:

You can see that target library ('groovy-1.7.2') is configured for the module:


But it's not displayed at 'Artifacts' dialog:

I managed to add it via the following actions:

1. Click 'Add' button (check screenshot above);
2. Select 'Library Files' context menu action;
3. Opened dialog shows target library and allows to add it to the artifact:

Denis

What files are included in 'SimulationLibs' library? Libraries without classes won't be shown in the 'Available elements' tree.

Unfortunately, no, it does not appear to be this issue.  This does not just happen after a new library is created, and I cannot get the module library to appear in the interface.  I've tried many permutations of actions to make this work. 

I'm attaching screenshots just to clarify.

Here are the relevant module dependencies:
Image:Screen shot 2010-05-12 at 1.33.14 PM.png

And here's the artifact editor:
Image:Screen shot 2010-05-12 at 1.32.06 PM.png

Note "SimulationLibs" is missing, and idea doesn't even warn me that it is missing.

Now, here's another piece of information, which may or may not be relevant.  I have a strange project structure, because I was trying to figure out how to organize project / modules.  My project dir is ~/DEV/foo  and my modules are all in ~/DEV/foo-modules.  I'm wondering if this is breaking some assumption about where module info is kept?

Appreciate any help - this is not a roadblock, but is an inconvenient bug.

thx,
josh

---
Original message URL: http://www.jetbrains.net/devnet/message/5263109#5263109

--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"SimulationLibs" contains many jars, all within the "lib" directory of the module.  Screenshot included:


Thanks,
Josh

Interesting;  I'm not sure this is exactly the same bug, though.  In your case, groovy is a project library; in mine, it is a module library.  It does not show up in the "add library" dialog.




However, if I change the library to be a project library (rather than a module library), it becomes available in the dialog:




This does not however make it available in the regular view of the artifact editor, nor does Idea warn me about the missing library.

Feeling a little like Sherlock, now.   My current best guess is that indeed this is a result of my weird project configuration.  Can you replicate with a project structure described above, where the project files are kept in /foo and module sources in a parallel directory /foo-modules?  I'm not sure what the critical factor is.

I wasn't sure at first, but think this is pretty clearly a bug.  I'm just not sure if it should be appended to the issue you've referenced, Denis, or should become a new issue.

Thanks,
Josh

Message was edited by: Joshua Introne - s/was sure/wasn't sure/

Feeling a little like Sherlock, now. :)

That it's definitely a bug and it's not clear whether it's the same as the referenced one or not. I'd suggest to do the following:

1. Wait for the referenced ticket to be fixed;
2. Check if everything is ok now;
3. Submit new dedicated request if the problem still remains;

Ok, great.  Thanks for the good advice.