Closed GoogleCodeExporter closed 9 years ago
Looking at the code, this is due to no ivy.xml being defined for module.
Rather than
throwing the NPE, it would be better to either:
A. Not have the option to resolve until you set ivy.xml (have it disabled in the
pop-up menu)
B. Take the user to the ivy module config screen to have them fill out the
ivy.xml
C. Have a pop-up indicting that the ivy.xml has not been defined for the module.
Original comment by borg...@gmail.com
on 27 May 2009 at 1:36
Hi borgees,
I had the same issue as you ... not able to open the module settings.
To avoid the NPE you can open your <module>.iml file inside IntelliJ and search
for
"IvyIDEA".
You'll find an entry like <configuration ivyFile="" .... /> just change the
ivyFile
attribute and put anything there <configuration ivyFile="foo" ... /> (or better
the
absolute path to your ivy.xml file).
Then you should be able to open the module settings (even if the ivyFile
doesn't
exist!!).
Hope it helps.
Original comment by juanhern...@gmail.com
on 30 Jul 2009 at 3:08
Original comment by aefimov....@gmail.com
on 27 Feb 2011 at 9:03
It fixed already in last repository version
Original comment by aefimov....@gmail.com
on 27 Feb 2011 at 10:23
Original issue reported on code.google.com by
borg...@gmail.com
on 26 May 2009 at 9:28