IvyDE
  1. IvyDE
  2. IVYDE-293

The 'Resolve all' button in the tool bar does not resolve all Ivyde containers in all projects, just the first Ivyde container in each project

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0.final
    • Component/s: None
    • Environment:

      Description

      I use multiple Ivyde containers in my Tomcat projects in Eclipse to distinguish between compile-time (e.g. servlet-api + jsp-api) and runtime (e.g. mysql) jars. But only one of the Ivyde containers gets resolved when I hit the 'Resolve all' button.

        Activity

        Hide
        Nicolas Lalevée added a comment -

        I have a test project which have two containers, and both get resolved, I can see it in the Ivy console and in the project with the containers being filled with jars.

        Can you detail you setup ?
        What detail make you think the resolve doesn't happend ?

        Show
        Nicolas Lalevée added a comment - I have a test project which have two containers, and both get resolved, I can see it in the Ivy console and in the project with the containers being filled with jars. Can you detail you setup ? What detail make you think the resolve doesn't happend ?
        Hide
        Thomas McCorkell added a comment -

        I'm also seeing this. I'm using Apache Ivy 2.3.0.cr120120416000235 and Apache IvyDE 2.2.0.beta1-201203282058-RELEASE.

        I have multiple containers in my build path, each referring to a different single configuration from the same ivy.xml (for example, one container for "build", one container for "runtime", one container for "test-build" and one container for "test-runtime"). Right-clicking on a project and picking "Resolve" results in only one container being resolved (always the same one in a given project). Clicking the "Resolve all" button in the toolbar results in only one container in each project being resolved.

        The easiest way I've found to check if this is happening is to clean the Ivy cache, then close and re-open the affected project. This results in all Ivy containers being empty until they are resolved.

        Show
        Thomas McCorkell added a comment - I'm also seeing this. I'm using Apache Ivy 2.3.0.cr120120416000235 and Apache IvyDE 2.2.0.beta1-201203282058-RELEASE. I have multiple containers in my build path, each referring to a different single configuration from the same ivy.xml (for example, one container for "build", one container for "runtime", one container for "test-build" and one container for "test-runtime"). Right-clicking on a project and picking "Resolve" results in only one container being resolved (always the same one in a given project). Clicking the "Resolve all" button in the toolbar results in only one container in each project being resolved. The easiest way I've found to check if this is happening is to clean the Ivy cache, then close and re-open the affected project. This results in all Ivy containers being empty until they are resolved.
        Hide
        Thomas McCorkell added a comment -

        This is also happenning if I right-click and pick "Resolve" while multiple Ivy containers are selected.

        Show
        Thomas McCorkell added a comment - This is also happenning if I right-click and pick "Resolve" while multiple Ivy containers are selected.
        Hide
        Kevin Formsma added a comment -

        I've seen issues similar to this, but it usually occurs after I've made modifications to the ivysettings file or if the cache changes externally.

        Show
        Kevin Formsma added a comment - I've seen issues similar to this, but it usually occurs after I've made modifications to the ivysettings file or if the cache changes externally.
        Hide
        Thomas McCorkell added a comment -

        @Kevin: I don't think that's the case for me. The ivysettings.xml hasn't changed and Eclipse is the only thing accessing the Ivy cache (and this occurs even with only one Eclipse instance running).

        Show
        Thomas McCorkell added a comment - @Kevin: I don't think that's the case for me. The ivysettings.xml hasn't changed and Eclipse is the only thing accessing the Ivy cache (and this occurs even with only one Eclipse instance running).
        Hide
        Nicolas Lalevée added a comment -

        I have found the underlying issue. If there are several resolves happening, and some of them are sharing the same ivy.xml, and the workspace resolver is enabled, then only one is actually done.
        I fixed that.

        Show
        Nicolas Lalevée added a comment - I have found the underlying issue. If there are several resolves happening, and some of them are sharing the same ivy.xml, and the workspace resolver is enabled, then only one is actually done. I fixed that.

          People

          • Assignee:
            Nicolas Lalevée
            Reporter:
            GK Ephorus
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development