When deploying a maven project that has an EAR via Run or Debug mode to Weblogic 10.3.5 the server starts processing the deployment but fails to find dependencies during the deployment.

Looking at the steps in the deployment the following step appears to be the one dropping the dependencies:

Initial deploying XXX-ear to C:\XXX\XXX-ear\target\wldeploy\XXX_XXX-ear_ear_1.0.2-SNAPSHOT
Completed initial distribution of XXX-ear

[Note: replaced client specific info with XXX]

In the wldeploy artifact directory only the web and ejb projects show up (as folders).  There are no dependency jars.

This problem goes away if I revert back to daily build 20121013. When I go back to that version the wldeploy directory has my web and ejb project directories as well as all the maven dependency jars loaded in the directory so the EAR has all the required dependencies during the deployment.

It also appears to be broken in daily build 20121119 and 20121127.

I just loaded the NetBeans 7.3 Beta 2 and gave it a try.  It has the same problem.  I am now trying to identify the module that changed so I can revert back so I can continue using the latest release (minus the offending module) with WebLogic.

I ended up copying the enterprise module jars from 20121013 to the latest version to get it to work.  Looking at the plugins check updates, it looks like the following are showing they were updated.  Here is my list of versions and the internal updates that would have happened if I followed the Check for Updates suggestions.

RichFaces: 1.19 
  Internal Updates
    J2EE DD API [1.27.0.2->1.28.0.2]
    Maven Java EE [1.29->1.30]

Oracle Cloud: 1.3.0.1.1
  Internal Updates
    J2EE Deployment and Management APIs [1.25->1.26]
    Java EE Core APIs [1.14->1.15]
    Java EE Specifications Support [1.9->1.10] 

Java EE Base: 1.18
  Internal Updates
    Bean Validation [1.9->1.10]
    EjbJar APIs [1.28->1.29]
    Generic J2EE Server Plugin [1.23->1.24]
    J2EE Server Ant Tasks [1.26.0.1->1.27.0.1]
    J2EE Support Utilities [1.73->1.74]
    JBoss Application Server [1.28->1.29]
    Java EE 6 API Library [1.13->1.14]
    Java EE Deployment Descriptor Loaders [1.25.0.2->1.26.0.2]
    Java Enterprise Samples [1.20->1.21]
    Oracle WebLogic Server [1.28.0.1->1.29.0.1] 

GlassFish v1, v2.x: 1.13.0.1 
  Internal Updates
    GlassFish Application Server Common APIs [1.24.0.1->1.25.0.1]
    sun-* DD API [1.25.0.1->1.26.0.1]
    sun-* DD GUI Editors [1.26.0.1.1->1.27.0.1.1]

Entity Relationship Diagram Support: 1.4
  Internal Updates
    Java EE Server Registry [1.93.0.1->1.95.0.1] 

EJB and EAR:  1.17
  Internal Updates
    Application Client (CAR) Module Projects [1.28.0.1->1.29.0.1]
    EJB Refactoring [1.17->1.18]
    EJB Verification [1.19->1.20]
    Enterprise Applications (EAR) Projects [1.32->1.33]
    Enterprise JavaBeans (EJB) Module Projects [1.36->1.37]
    Enterprise JavaBeans Core [1.31->1.32]
    Java EE Documentation [1.23->1.24] 

CSS Source Model: 1.12
  Internal Updates
    Web Services Deployment Descriptor API [1.23->1.24]

One of them is forcing the inclusion of the offending jar.

I hope this can be resolved prior to next beta or release candidate.  :-)

Thanks,
Dave