By default we have MyEclipse->Maven4MyEclipse->Resolve dependencies from Workspace projects configured to be on. This generally works well for us.

However when we close a maven project that a Maven Webapp depends on, we get the following error for the webapp: "Invalid classpath publish/export dependency [project that was closed]. Project entries not supported.

We have found that we can get rid of the error by configuring the webapp by unchecking "Resolve dependencies from Workspace projects" and apply the change. Once it has been applied the error goes away and all is happy... accept we cant resolve workspace dependencies. Luckily we can immediately go recheck it and apply it again and now all the non-closed dependencies will be resolved and the closed project dependency will be fetched from our company repo.

So what I was wondering is if there is some bit of obvious project configuration we are missing or to know if this is a known issue so we can stop thinking about it and just deal with the mild annoyance.

MyEclipse version: 10.5-20120615

jgarrison,

I've filed a bug for this issue, we'll investigate and get back to you on whether a workaround is possible. There is no configuration or preference that would change this behavior, but perhaps we'll be able to put a fix into our next release.

Thank you for your report.

jgarrison,

I have reproduced your issue and I have found that you can run Maven4MyEclipse -> "Update project dependencies" on the selected project from popup menu, which will remove the error. This action is intended to be used in case of such problems. Also, if the project got replaced with a JAR from repository in Maven Dependencies container, you can safely remove the error from problems view by simply deleting it (right click -> delete) without running Update project dependencies action. I hope this solution will be agreeable for you. Let me know how it works for you!

Hi,

Thanks for the reply. We had previously been just doing Maven4MyEclipse -> Update Dependencies and that wasn't getting rid of the error. Following Piotr's advice I did Maven4MyEclipse -> Update Project Configuration and that solved the issue.

If the bug Brian submitted is still open I think a nice enhancement would be to run this automatically when a dependency is closed.

Thanks for the help