Yes, we do the same thing. How to solve changed with M2. Now, use <scope>system</scope> and <systemPath>.
I think this JIRA discusses what your issue is. Brett described the un-recommended workaround. http://jira.codehaus.org/browse/MNG-1471 I look forward to reading your comments on this... :-) Quoting Matthew Wheaton <[EMAIL PROTECTED]>: > Hi all, > > In Maven 1.x, I could get a list of the jars in my version control > repository, and dynamically add them to the Maven build path using an ant > task. > What's important to note, is that I have all my dependency jars in a few, > KNOWN directories. I would like to be able to include all those jars, > without having to reference each one of them explicitly in a POM, or a > parent POM. Below is how I do this in Maven 1.x with the ANT task. Note > below, that I can create the ant goal, however, the last line in the goal, > seems to be only an Maven 1.x feature and not possible in Maven 2.x. > > In our environment, we may have totally different people developing that the > people doing the build. When a developer adds new JARs to version control, > it will break the build, unless we manually add the reference in all the > associated POMs (or parent POMs). We're trying to avoid this, any ideas ? > > Below is my Maven 1.x ANT goal. > > <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> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
