Hi Matthew,
You should specify the scope of your dependency in the pom.xml file. If
the scope is set to "compile" (default value), then the dependency will
automatically be included in the compile time classpath. If it is set to
"runtime", then the dependency would be added in the runtime classpath
by maven. And so on..
Check out the Dependency Mechanism section
(http://maven.apache.org/guides/index.html) of the Maven 2 documentation
for more details.
Regards,
Odea Ching
Matthew Wheaton wrote:
Hello,
I am an avid Maven fan, and am struggling to understand how to model my new
projects based on my Maven 1.x experience.
I have a number of Eclipse projects, one called csi_libs.
csi_libs, contains all the compile time (and some deployment) 3rd party jars
needed across all projects.
In Maven 1.x, I simply had a simple Ant task that added all the jars to the
classpath for builds, like so:
<goal
name="build:SetClasspath"
description="Sets the classpath">
<echo message="Setting the compile classpath . . ." />
<ant:path id="all.libs.path">
<!-- get all the deployment libs -->
<ant:fileset dir="${build.deployLibs}">
<ant:include name="**/*.*" />
</ant:fileset>
<!-- get all the compile only libs -->
<ant:fileset dir="${build.compileLibs}">
<ant:include name="**/*.*" />
</ant:fileset>
</ant:path>
<m:addPath id="maven.dependency.classpath" refid="all.libs.path" />
</goal>
I'm struggling on how to replicate this behavior in Maven 2.
Anyone out there who can assist ?
Thank you.
Sincerely,
Matthew Wheaton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
