If you want to use a maven pom.xml instead of ivy.xml file, you just have to select a pom file in the configuration form of IvyDE class path. When a maven pom is selected, the configurations list is updated with all maven scopes. Both examples below are a good illustration of maven pom use simplicity :
Maven1 sample
Maven2 sample
Maven1 Sample
This sample presents a simple use case of maven pom for IvyDE class path container. We are going to create an eclipse project on commons-httpclient sources.
- Download the
commons httpclient sources
- Unzip this file (c:/tmp/commons-httpclient/)
- Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)
Notes:
your project do not compile: some imports cannot be resolved.
- Add a new class path container based on the "project.xml" pom and select "default" configuration (maven scope)
- That's all : your project compiles !
Maven2 Sample
This sample shows that IvyDE Class path container on a Maven2 pom can handle transitive dependancies.
- Create a new empty java project in eclipse.
- In your project, create an
ivysettings.xml
file:
Using the m2compatible attribute, you can benefit from Maven2 repository compatibility.
- In your project, create a
pom.xml
file:
4.0.0
com.mycompany
myproject
1.0-SNAPSHOT
commons-httpclient
commons-httpclient
3.0
- On the pom.xml file, open the context menu and click on "Add Ivy Library...":
Select "Enable project specific settings" and set the "Ivy setting path" to:
project:///ivysettings.xml
Select the configuration
compile
and
runtime
- That's all ! Your IvyDE class path container gets all dependencies even those that were transitive to the commons-httpclient module !