Overlay [xxxxxx] is not a dependency of the project

The problem comes from the way the command line processes the dependencies vs how the plugin processes dependencies.

From the command line I get a dependency list like the second image

If done from the command line, the weblogic jar is include as a classpath entry. here, all the files referenced in the weblogic.jar META-INF/manifest classpath are added to the classpath.

When referenced from the plugin, the weblogic jar is placed inside of the “maven dependencies” which does not include the other jars which are listed in the manifest.

(VERY BIG problem with the plugin imo). This basically will make the maven plugin somewhat limited to simple projects.

Editorial comment:

I hate what weblogic did with the manifest. This has caused numerous build issues for us with outdated jars being included. However, we are kinda stuck with this for now.

sorry for the confusion.

Both eclipse and the command line are pointing to the same instance of maven
C:\development\Workspace>mvn -version
Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
Maven home: C:\development\software\tools\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_24\jre
Default locale: en_US, platform encoding: Cp1252
OS name: “windows vista”, version: “6.0”, arch: “x86”, family: “windows”
C:\development\Workspace>

The two differences from the above show what happens if

a:

I issue a mvn eclipse:eclipse or (mvn eclipse:myeclipse)

b:

I right mouse over the project and say update project configuration.

In the first case – when I include weblogic I get all of the items included in the manifest.

In the second case – when I include weblogic, i do not get the items in the manifest.

The weblogic.jar does not have a POM so there are no maven transitive dependencies.

I believe you are not experiencing the problem because you put the weblogic jar in the repository. This will generally not work as expected. Inside of the weblogic jar is the manifest with the following: Notice all of the of the relative classpath items. many of the jars on the classpath have a manifest that includes other jars (again relative to their location).

If you just use a repository – none of the associated jars will be found and you will encounter many errors when you need a JMS, or JTA, or WS or any weblogic specific items. (been down that path).

we have been forced to include the bea.home in our settings file.

<properties>
<ccic.snapshots.repo>http://ccicusbuild1/nexus/content/repositories/snapshots/</ccic.snapshots.repo&gt;
<bea.home>C:/development/software/bea/bea10.3.2</bea.home>
<bea.lib>${bea.home}/wlserver_10.3/server/lib</bea.lib>
</properties>

Implementation-Title: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PD
T 2009 1267925
Implementation-Version: 10.3.2.0
Class-Path: ../../../modules/features/weblogic.server.modules_10.3.2.0
.jar schema/weblogic-domain-binding.jar schema/weblogic-domain-bindin
g-compatibility.jar schema/diagnostics-binding.jar schema/diagnostics
-image-binding.jar wlcipher.jar webservices.jar xmlx.jar ojdbc6.jar a
qapi.jar EccpressoAsn1.jar EccpressoCore.jar EccpressoJcae.jar mysql-
connector-java-commercial-5.0.3-bin.jar wlsqlserver.jar wldb2.jar wl
sybase.jar wlinformix.jar wlw-langx.jar ../../common/lib/pdev.jar jco
m.jar weblogic-L10N.jar

We have defined a property called bea.home and bea.lib

then we use a system dependency like this

<dependency>
                <groupId>com.bea.weblogic</groupId>
                <artifactId>weblogic</artifactId>
                <version>10.3</version>
                <scope>system</scope>
                <systemPath>${bea.lib}/weblogic.jar</systemPath>
            </dependency>