Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Still run into m2e not setting newly imported projects as java projects, with minimal maven info

Can you attach the projects (before import), without the source code, and after anonymizing the poms?

On Wed, Jul 10, 2019 at 10:30 PM KARR, DAVID <dk068x@xxxxxxx> wrote:
I work on a team with a bunch of git repos that are Java, Maven, and Spring Boot projects.  We all configure Eclipse somewhat similarly, although I'm sure many of the other developers on the team have variations that I don't expect.  We install the Spring IDE and Groovy plugins, and we (not all of us) are on 2019-06.

There is one project that occasionally presents problems, perhaps because it has one additional element that other projects don't have.  It uses the "jsonschema2pojo-maven-plugin" and "build-helper-maven-plugin" to generate class files for json marshalling.

Typically, when I import projects, I right-click on the git repository entry and select "Import Projects...".  This works fine for almost everything I work on, but it occasionally has trouble with this project.  I had this working in my workspace, but another developer reported problems with this, and I couldn't get it to work on his, so I removed my imported project (which was currently working fine), along with the .project, .classpath, and .settings, and tried importing it again, and it's not working properly, similar to what he is seeing.

I've now tried importing the project both with "Import Projects..." and "Import Existing Maven Projects", and the results are basically the same.  The result is that it doesn't think it's a Java project, and it doesn't recognize the existing src/{main,test}/java folders, not to mention the target/java-gen folder where the generated classes are stored.  It does acknowledge it's a Maven project, but nothing works because of those other problems.

Fortunately, I have a workaround, but it's not very good.  I simply ask someone else who has this project opened, who does not have this problem, to send me their .project and .classpath files, and I copy them in, and then reimport the project.  It is now fine.

If it will help, right now I could provide the .project and .classpath file that we need for it to work.  I could iterate through this scenario again (first saving those two files in a safe place) and produce the original resulting dot files, if you think that would be useful.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/m2e-users


--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5

Back to the top