maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thor <>
Subject Include provided dependencies in MANIFEST
Date Mon, 25 Feb 2008 21:45:44 GMT
Sorry people the original subject was very wrong and confusing...

---------- Forwarded message ----------
From: Thor <>
Date: Mon, Feb 25, 2008 at 3:43 PM
Subject: Include provided dependencies in jar
To: Maven Users List <>

Hello everyone, thanks for reading.
I have a JEE project with several modules:
- project-api
- project-core
- project-ejb
- project-view
- project-ear

On my server (OC4J) I have shared several common libraries for all the
deployed applications, like jakarta-commons, spring, and so on

On my project-ejb's pom.xml file I've configured these dependencies as
"provided" in order to avoid including these jars into my ear when i make a
"mvn install"

I need the OC4J to be aware of these dependencies, so I've configured the
Maven Archiver to include the classpath in the manifest file. The problem is
that when i build the project, it completely ignores the "provided" scoped
dependencies and doesn't adds them to the generated
So far I've tried several combinations with the <scope> and <optional>
dependencies attributes, but nothing seems to work.
Here's a portion of my pom:
<!-- More dependencies here -->

Any hints or directions would be very appreciated...
Thanks in advice.

(o_ \*
/ / ) |

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message