Classpath in referring projects seems to include sources/binaries from other open projects before/instead of installed artifacts in the local repository

When one Maven project references another, the referenced project's readily packaged artifacts - as installed into the local repository - should end up in the classpath of the referencing project. With the current Mevenide 3.0.x, it seems like the compiled classes of the original NB project themselves are directly put into the referring project's class path instead. This definitely breaks when some post-processing happens in the referenced project between the compile step and the install step, such as e.g. in my case static weaving/bytecode generation. In my case, this means that I have lots of compilation errors in the depending projects, and cannot properly write code that uses the modified classes...

Reply by Milos on the mailing list:

"unfortunately either way it will make some people unhappy. I had requests to link to the opened project sources/binaries without the need to do mvn install. That's how netbeans ant project reference work I believe."

My conclusion/wish:

Sounds to me like the best solution would be to make it configurable in the global Mevenide configuration dialog whether sources/compiled classes from referenced open projects or the installed jars from the local repository end up in the referring project's classpath...

Many thanks in advance!