Categories


Authors:
mahieugu
logos
Apache

IvyIDEA

Vendor: Guy Mahieu

Email:

Website: http://www.ivyidea.org

SourceCode: link

Description:

Resolves module dependencies through Ivy

Features:

  • Ivy integration (up to v2.0.0rc2); no need for external ant build scripts to be called
  • Automatic ivy configuration of modules using facets (for modules containing an ivy.xml file)
  • Detection of dependencies that are really other intellij modules in the same project; these are added as module references
  • Detect source/document/jar type ivy artifacts in dependencies and add them as such to the module
  • Creation of a module library with all resolved ivy dependencies
  • Ivy configurations that need to be resolved can be chosen for each module

Downloads: 3717
Rating:
Participated in rating: 5
Version Since Build Until Build File/URL Size (Kb) Date Dependency
0.8. 40.3000. . Download 910.49. 2008-12-10 20:55:36 .
0.7-alpha. 40.3000. . Download 894.7. 2008-11-12 19:14:44 .
0.6-alpha. 75.7757. . Download 892.44. 2008-10-30 13:36:54 .
0.5-alpha. 75.7757. . Download 894.49. 2008-10-29 23:29:13 .
0.4-alpha. 40.3000. . Download 865.98. 2008-10-22 19:50:07 .
0.3-alpha. 40.3000. . Download 865.04. 2008-10-21 00:47:34 .
0.2-alpha. 40.3000. . Download 862.41. 2008-10-20 22:13:53 .
0.1-alpha. 40.3000. . Download 861.96. 2008-10-19 17:18:22 .
. .
IvyIDEA

Recent change notes:

0.8

  • Upgraded internal ivy to 2.0.0rc2
  • Improved exception handling
0.7-alpha
  • IvyIDEA is now compatible with IntelliJ 8.0 (and will run on previous versions as well)
  • Switched to JDK 1.5 so the plugin will also run on mac os
  • Made looking up intellij module dependencies more lenient; now the revision is ignored when identifying dependencies as existing intellij modules rather than jars
0.6-alpha
  • Removed toolwindow logging again as a quickfix - it blocked UI on larger projects.
0.5-alpha
  • The ivy configurations that need to be resolved are now configurable. They can be selected in the module configuration.
  • Dependencies that are in the module library from a previous resolve, but that are no longer valid are now removed during the resolve process.
  • Resolve process is now done in a background task to avoid blocking the UI.
  • Added a first simple toolwindow with the logging from the ivy resolve process.
0.4-alpha
  • Added option in project settings to allow resolving without validating ivy.xml files
0.3-alpha
  • Fixed issues with non-ivy modules mixed with ivy modules in one project
  • Added menu item to allow removing all resolved libraries in the project
0.2-alpha
  • Fixed an annoying bug causing exceptions when dependencies were evicted

General usage instructions:

Configure the ivysettings file (usually called ivyconf.xml or ivysettings.xml) in the project settings. Add an IvyIDEA facet for every module you have that uses ivy (if it was not autodetected already) and point it to the ivy.xml file for that module. You can now resolve your dependencies through the Tools > IvyIDEA Resolve menu or through the right click menu of the project explorer.

Comments:

Anonymous
Rated:
2009-01-14 09:17:51
The first ivy plugin that does the job!
.
Anonymous
Rated:
2009-01-12 14:17:00
this is the way to do it: simple seamless ivy dependency integration.
.
Anonymous
Rated:
2009-01-07 16:22:25
The plugin is well done, but what I still miss is the possibility to define a different ivy configuration during compile and packaging of my war files.

It would be great to use a "compile" or "test" configuration for compiling and junit testing. The "runtime" or "deploy" configuration could then be used for packaging only those libs inside the war.
.
Anonymous
Rated:
2009-01-04 22:17:41
.
Anonymous
Rated:
2009-01-04 22:01:19
simplicity!
.