Michael Thompson created IVYDE-393: -------------------------------------- Summary: Ivy Nature is spreading from parent projects 2.3.0.rc1-201806251008-RELEASE Key: IVYDE-393 URL: https://issues.apache.org/jira/browse/IVYDE-393 Project: IvyDE Issue Type: Bug Components: classpath container, workspace resolver Affects Versions: master Environment: IvyDE: 2.3.0.rc1-201806251008-RELEASE
Eclipse Version: 2019-09 R (4.13.0) Build id: 20190917-1200 Reporter: Michael Thompson Fix For: master Attachments: image-2020-04-29-13-29-22-972.png, image-2020-04-29-13-32-55-798.png, image-2020-04-29-13-34-15-720.png I have a parent project that has my Ivy dependencies exported for use in other projects. Periodically IvyDE tries to add the "Ivy Nature" to those child projects (which are RO) and then things fail with "The ivy.xml file was not found". I had the same issues 2.2.0 before I upgraded. Is there anyway to stop this? I don't want to have to maintain an ivy.xml for every child project. As a workaround I can click Ivy/Remove Ivy dependency management but it will eventually come back randomly. This is the parent: !image-2020-04-29-13-29-22-972.png! This is an example child which references it and passes it on to further children: !image-2020-04-29-13-32-55-798.png! and also has (in memory at least) the Ivy nature when it shouldn't: !image-2020-04-29-13-34-15-720.png! When it is working though it works great! Thanks, Michael Thompson -- This message was sent by Atlassian Jira (v8.3.4#803005)