IvyDE
  1. IvyDE
  2. IVYDE-178

Ivy Library removed from the list of Java EE Module Dependencies after changing its properties

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.0
    • Component/s: classpath container
    • Labels:
      None
    • Environment:

      Eclipse Version: 3.4.2
      Build id: M20090211-1700

      Description

      When changing the properties of the ivy Library (e.g. deselecting a configuration), the ivy library is deselected in the list of Java EE Module Dependencies.

        Activity

        Hide
        Nicolas Lalevée added a comment -

        From the pure user point of view this is a bug, but the Eclipse API doesn't offer much options about it. Each time the properties of the classpath container is changed, its id (in Eclipse API its "path") change, and then the wtp consider it a new container.
        Maybe we will find one day a clean way to handle container paths, maybe via attributes?

        Show
        Nicolas Lalevée added a comment - From the pure user point of view this is a bug, but the Eclipse API doesn't offer much options about it. Each time the properties of the classpath container is changed, its id (in Eclipse API its "path") change, and then the wtp consider it a new container. Maybe we will find one day a clean way to handle container paths, maybe via attributes?
        Hide
        Jeffrey Sinclair added a comment -

        This also causes a problem using Ivy Managed Dependencies with the AspectJ plugin (AJDT). AJDT adds the following attributes:

        <attributes>
            <attribute name="org.eclipse.ajdt.aspectpath.restriction"  value="tracing"/>
            <attribute name="org.eclipse.ajdt.aspectpath" value="org.eclipse.ajdt.aspectpath"/>
          </attributes>
        

        to an Ivy ClasspathEntry which get deleted when changing any ivy related properties.

        Show
        Jeffrey Sinclair added a comment - This also causes a problem using Ivy Managed Dependencies with the AspectJ plugin (AJDT). AJDT adds the following attributes: <attributes> <attribute name="org.eclipse.ajdt.aspectpath.restriction" value="tracing"/> <attribute name="org.eclipse.ajdt.aspectpath" value="org.eclipse.ajdt.aspectpath"/> </attributes> to an Ivy ClasspathEntry which get deleted when changing any ivy related properties.
        Hide
        Nicolas Lalevée added a comment -

        IvyDE manage now its setup also via some attributes and manage correctly the ones it doesn't know.
        So it will also fix your issues Jeffrey with AspectJ.

        Show
        Nicolas Lalevée added a comment - IvyDE manage now its setup also via some attributes and manage correctly the ones it doesn't know. So it will also fix your issues Jeffrey with AspectJ.
        Hide
        Stefan Sieber added a comment -

        Thanks a lot Nicolas!

        2009/9/14 Nicolas Lalevée (JIRA) <jira@apache.org>

        Show
        Stefan Sieber added a comment - Thanks a lot Nicolas! 2009/9/14 Nicolas Lalevée (JIRA) <jira@apache.org>

          People

          • Assignee:
            Nicolas Lalevée
            Reporter:
            Stefan Sieber
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development