Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 1
    I can confirm it solves problem with workspace resolution for dependencies with classifier; typically war projects with attachClasses=true. However, drawback is that now versions between dependency reference and referenced project must perfectly match, otherwise it is instaly reported as broken dependency. In practical term it means a lot more of git checktouts. Commented Nov 3, 2015 at 17:55
  • I'm having this problem when I have the dependent project opened in the workspace and try to add/remove the consuming project (that relies on the dependent war project) to Wildfly-10. If I have the project open in the workspace the <artifact>-classes.jar is not present in the deployed project, hence deployment fails. However, if I delete the project from the workspace the library IS included in the project and deployment is ok. I tried the workaround you described, but after reading into it, I don't think it really applies to my problem. Builds in eclipse also succeed without the workaround... Commented May 8, 2018 at 8:49