Setting up Maven build of your custom WebLogic security providers is no trivial task. This post describes some of the pain you have to go through, but does not take you quite all the way. It still depends on WebLogic being installed. This makes assumptions about machines where maven will run on.

To solve this problem you need to pass -Dweblogic.home=${project.build.sourceDirectory}/.. parameter to WebLogicMBeanMaker subprocesses to trick it into using location of your choice. This can be done like this

java weblogic.management.commo.WebLogicMBeanMaker -jvmArgs “-Dweblogic.home=${project.build.sourceDirectory}/..” …

This fake WebLogic home location should be part of your project and fixed relative to your source. All you need to do to set it up is to add <WEBLOGIC_HOME>/lib/schema/weblogic-domain-binding.jar to your ${project.build.sourceDirectory}/../lib/schema/ as well as <WEBLOGIC_HOME>/lib/mbeantypes/wlManagementImplSource.jar and <WEBLOGIC_HOME>/lib/mbeantypes/wlManagementMBean.jar to ${project.build.sourceDirectory}/../lib/mbeantypes.

Check out your typical BEA sample security providers project that can be built with maven here.