I wanted to file this so people are aware.
In our project, we originally had a wrapped jar shared between all our modules. This was eventually found to be impractical, and was replaced with a Module Dependency that contained the one wrapped jar, and shared it's packages publicly to all the modules.
We removed the wrapped jars in the IDE and linked up the Module Dependency.
However, either because of SVN or if the IDE failed to removed the wrapped jars, the jar was left behind inside of release/module/ext.
When we ran the project, the left over wrapped jars were loaded OVER the module dependency, and we were using old versions of code that wouldn't update, no matter how many times we recompiled the modules.
This is simple to replicate.
1 - Create module A that is using a wrapped jar.
2 - Create a new module B that will be used as a dependency that contains the wrapped jar. Update the wrapped jar that B uses so it differs from A.
3 - Remove the wrapped jar from A. Make sure the jar is still within A/release/modules/ext
4 - Add B as a dependency for A.
5 - Compile and run.
Thanks for the note. As this is clearly a user error (e.g. no practical usecase, right?), I am not sure it makes sense to try to fix it.
(In reply to Jaroslav Tulach from comment #1)
> Thanks for the note. As this is clearly a user error (e.g. no practical
> usecase, right?), I am not sure it makes sense to try to fix it.
Agreed. I posted this up because I found a lot of misleading and confusing links online, and made this so maybe this could help anyone else who may run into this problem.
Maybe Geertjan wants to document it somewhere. Or I can do it, if you tell me what would be the best place in documentation to put a note about that.
Maybe UtMan88@netbeans.org can write a small tip/article about this on http://netbeans.dzone.com and add a new FAQ about it here:
FAQ seems like a really good option. Thanks for pointing that out Geerjan.