Sporadic problems deploying projects on Build Path within Eclipse

Question

Hi
We're using OEPE 1.8.0 with Weblogic 10.3.2 to run our projects within Eclipse and are deploying to the local server using the "Exploded archive" option (we cant get "virtual application" to work with EJB's).
The entire codebase is using Maven, so we run m2e (the latest Indigo version 10.0.100) and the projects are imported using the "Existing Maven Projects" option.
We're experiencing 2 distinct and very sporadic problems, which has haunted us through, well, as far as I can remember, ever since we started using OEPE:
1) Sometimes when say an EJB depends on a project, OEPE deploys the root of the dependent module (i.e. the source) instead of compiled code - resulting in ClassNotFoundExceptions. The only remedy has been to evict the said dependent project from Eclipse and let the m2e point to the repository version instead.
2) This happens less, but happens non the less: Sometimes, again with EJBs, OEPE just omits a dependent project, without it reporting anything wrong with the module ("Module status" in the Error log states that the dependent module is known, but never packs it).
(We're deploying the EJB's in EAR's)
The above problems only happens when the projects are in Eclipse (not when referred to from the Maven repository). There are no errors packing the projects in any logs.
I would expect this to be a problem within the packager producing the "Exploded Archive" and maybe in conjunction with m2e. I havent done extensive testing without m2e (we had the problem way before Indigo as well, when m2e was m2eclipse).
These are the only gripes we have with OEPE in relation to running our applications during development, but we're spending hours resolving these issues when they occur, as we havent found any sound explanation for the problem (it's trial and error until the problem goes away).
Anyone else having the above problems?
Regards
Erik Reuter

Answer 1

I answered my own question -
I had to manually add the following to the WEB-INF/lib to get the error to go away:
${ORACLE_HOME}/modules/javax.jsf_1.1.0.0_1-2.jar and
${ORACLE_HOME}/oracle_common/modules/oracle.jsf_1.2.9/glassfish.jsf_1.0.0.0_1-2-15.jar and
${ORACLE_HOME}/oracle_common/modules/oracle.jsf_1.2.9/glassfish.jstl_1.2.0.1.jar
that solved my problem. However, I think it'd be great if I could somehow just specify (in the weblogic-application.xml maybe?) that my application is using the above modules without having to copy the jar files into my WEB-INF/lib - any suggestions?
Thanks