Closed fralalonde closed 8 years ago
Yeah, there was a recent change that broke the development setup. The Maven poms only affect the build, they don't affect the development setup (unfortunately due to a limitation in the tools, these two things are setup separately, and sometimes they can get out of sync)
Ok! I'll resync later until it is fixed.
Thanks.
On 10/28/2016 1:43 PM, Bruno Medeiros wrote:
Yeah, there was a recent change that broke the development setup. The Maven poms only affect the build, they don't affect the development setup (unfortunately due to a limitation in the tools, these two things are setup separately, and sometimes they can get out of sync)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bruno-medeiros/MelnormeEclipse/issues/9#issuecomment-256983315, or mute the thread https://github.com/notifications/unsubscribe-auth/AF50tImSwK6gm5aj-j-V-A80AyuzVraAks5q4jRQgaJpZM4Kjm9t.
Hi, I've followed the Eclipse setup instruction to the letter but I'm still missing the Gson dependency for module LANG_PROJECT_ID.tooling. This results in classes melnorme.lang.utils.gson.GsonHelper and melnorme.lang.utils.gson.JsonParserX not compiling. Other than that, the project and modules loads successfully in Eclipse.
The only libs that show up in the generated target platform repository are JUnit (4.12) and Hamcrest (1.3.0). Should those even be there? From the command line, Maven successfully completes building both the root project and the target-platform project.
I'm using Neon.1 on Windows 10 x64 (if that changes anything)
I've searched around the poms, both immediate and in maven-jar. It is still not clear to me how the dependencies are declared and migrate from one layer to the other - I've tried changing the pom-declared Gson version to 2.7, but I still see 2.2.4 being referenced in the Maven debug trace.