ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Burcher (JIRA)" <>
Subject [jira] [Created] (IVYDE-307) IvyDE 2.2.0beta1 breaks using Run/Debug configurations with Ivy
Date Mon, 21 May 2012 10:05:41 GMT
Ed Burcher created IVYDE-307:

             Summary: IvyDE 2.2.0beta1 breaks using Run/Debug configurations with Ivy
                 Key: IVYDE-307
             Project: IvyDE
          Issue Type: Bug
          Components: classpath container
    Affects Versions: 2.2.0.beta1
            Reporter: Ed Burcher

In our multi-module ivy project we assemble services by composing them from (the artifacts
of) the functionally-aligned modules 

For debugging/running in eclipse, we use the IvyDE classpath container in the run configuration
as the only source of jar files (this avoids having to update loads of individual run configs
with explicitly named jar files whenever a new dependency is required by something). This
works very well with IvyDE 2.1.0 but breaks with IvyDE 2.2.0 beta1

Here's we set up a new run configuration:
- We have a dedicated 'ide' project to host run configurations.
- We have 'resolve before run' set up in the ivyde global settings
- In that project, we create a brand new run configuration in eclipse as normal. 
- When configuring it, we go to the classpath part and remove any existing 'User' entries.
Then we add the IvyDE classpath container (via Advanced / Add Library...). This is configured
as follows:
#1 on the settings panel use the workspace button to navigate to ivy settings (within our
build project, which must be in the workspace)
#2 on the ivy file panel type in a path that is relative to the ide project root (ivy/MyServer.xml)
where the ivy directory is immediately below project directory. 
#3 we have per project (to name the ivy branch, principally), so configure
that on the same panel (ivy/
- Hit Run. IvyDE will moan a bit (it doesn't like relative path refs to ivy.xml) but it works.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message