Compile errors in root project for child projects, which don't have errors

(davidmichaelkarr) #1

Using Neon.2 with BuildShip 1.0.21.

I’ve had a small multi-project build for several weeks now that is mostly working fine, with one perhaps minor problem.

The build itself is using Gradle 3.3, and it works fine from the command line.

There are only two child projects. When I imported the project, I got to a point where Eclipse didn’t have any red marks in the two child projects. That was good enough for me to work with.

What’s odd is that I have a bunch of errors in the top-level project, but they all refer to errors in files in the child projects, none of which actually have any errors.

For instance, one of the child projects is a Spring application. As I said, the child project itself has no errors, but in the top-level project, I see errors like “Autowired cannot be resolved to a type”, referring to a file in that child project.

Note that I’m using Buildship 1.0.21, which came with Eclipse. I’ve considered upgrading to the latest version, but I don’t quite understand the process of replacing the packaged version with a newer version. Is it possible this problem would be fixed by upgrading? I hope that doesn’t cause other problems.

(Stefan Oehme) #2

Sounds like your root project is somehow adding some subproject folders as source folders. Hard to tell without an example project.

(davidmichaelkarr) #3

That was it, of course. I never did that manually. I suppose I should be able to test this, by reimporting the project from git again. I’ll queue up a test for that.