Community
Participate
Working Groups
Upgraded from Juno to Luna (to get the standalone SONAR plugin) and one problem impacting the team's adoption is changes in one project are not being picked up in another, forcing command line recompilation using maven. Example: Project Memory Objects (depends on Base jar file) Project Base (depends on Memory Objects project) Project A (depends on Base and Memory Objects project) Project B (depends on Base and Memory Objects project) Project Runner (depends on all projects) In Juno changes to Base where picked up however in Luna it appears that if any referenced project itself points to a jar file then the jar will be used as the source over the project. Due to a circular dependency we need to reference the same project in jar form (in this example 'Memory Objects' referencing 'Base' as a jar). This problem means effectively the IDE doesn't work as an IDE as we need to compile 'Base' from the command line (maven) so the changes are picked up by Project A, B and Runner. There may be a simple fix for this but not obvious what it is (removing the circular dependency unfortunately isn't an option in legacy code). Ideally eclipse should prefer a project as the source for the .java and .class file rather than take from jar files first.
Alex, To me, it is not clear enough to start an investigation. Could you please provide - a minimal workspace, (zip?) - steps to reproduce the issue - expected behavior Thanks and Regards.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
