New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eclipse m2e “Update Maven Project” adds an unneeded bin directory #1
Comments
@fbricon any ideas? |
I have never seen that issue. But I reckon it might happen if the project is imported with an existing .classpath pointing to bin/, before m2e updates the classpath. @ecmel can you still reproduce the problem? If so, do you have a sample project we can try? |
@fbricon I can not reproduce the problem with 0.0.7 |
fbricon
pushed a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Aug 21, 2017
* add initial debug plugin * add debug project in language server product * add copyright, remove startup class.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
This issue effect this project as well:
http://stackoverflow.com/questions/13853902/eclipse-m2e-update-maven-project-adds-an-unneeded-bin-directory
From the last answer:
"If you don't have a .classpath, upon cloning, java builder kicks in and messes things up before maven builder recreates a clean .classpath."
The text was updated successfully, but these errors were encountered: