What makes you think that Maven is "trying to reference some of the
jars... but is unable to find them"? Do you have something interesting
from mvn -X to show or just a general feeling in your gut about what
it is doing?

As far as I know (and I reserve the right to be proven wrong), Maven
definitely does not look at the Manifest.MF files in Jars in your repo
and then monkey around with dependencies etc. It only looks at the
dependencies declared in the various pom.xml files.

Wayne

On 1/23/08, robcon <[EMAIL PROTECTED]> wrote:
>
> In our Maven POM we have a dependancy on a jar (Weblogic.jar) which has many
> Jars listed in the  classpath Entry in its Manifest.MF file.
>
> When doing a Maven install maven appears to be trying to reference some of
> the jars in the classpath but is unable to find them because the
> weblogic.jar is in the Maven repository folder and the jars referenced in
> the classpath are in  the bea-weblogic  folder. Resolving the classpath jars
> appears to rely on all of the jars living in the standard weblogic folder
> structure.
>
> This must be a common problem. How do I get around this ?
> --
> View this message in context:
> http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15039656.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to