The workaround I've used is: - Ensure referenced projects' (all producing jars in my case) facet have them as Utility projects - Create references from the deployable to the utility projects
It works, but if it's a manual process it'll be an ongoing pain. We're generating out .project, .classpath, .settings/*, and related from our Ivy files, so it's not horrible in our case. hth, ~Tim On Thu, Dec 10, 2009 at 3:22 PM, Matt Benson <[email protected]> wrote: > So it appears that https://bugs.eclipse.org/bugs/show_bug.cgi?id=184125 is > the reason the workspace-resolved projects are not published to web servers > along with the other dependencies in the IvyDE library/classpath container. > So let's give them a barrage of votes on that 2+ year-old request. > > What do other people do about this lack? Select the projects as utility > jars? I hate that. Is it correct that a project's libraries must be > compiled against? I think that is the case, but if not it would seem that > creating a second library of class directories resolved from > workspace-resolved projects could work. I find this quite frustrating. > > -Matt >
