You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Rick Mann <rm...@latencyzero.com> on 2006/03/30 01:20:52 UTC

REPOST Still unclear on intended use of "useScope" in ant tasks

I looked through the archives and didn't find a satisfactory answer  
to this question.

We have an ant build script (and no POM) that we use to build our  
webapp. We have a single <artifact:dependencies> block:

	<artifact:dependencies	pathId="compile.classpath.maven"
							filesetId="libdeps"
							verbose="false">
		
		<remoteRepository refid="km.repository"/>
		<remoteRepository refid="main.repository"/>
		
		<dependency	groupId="javax.activation"		artifactId="activation"				 
version="1.0.2"		scope="runtime"/>
		<dependency	groupId="commons-beanutils"		artifactId="commons- 
beanutils-core"	version="1.7.0"		scope="compile"/>
		<dependency	groupId="commons-digester"		artifactId="commons- 
digester"		version="1.7"		scope="compile"/>
		<dependency	groupId="log4j"					artifactId="log4j"					 
version="1.2.12"	scope="compile"/>
		<dependency	groupId="mysql"					artifactId="mysql-connector-java"	 
version="3.0.16-ga"	scope="compile"/>
		<dependency	groupId="com.oracle"			artifactId="ojdbc"					 
version="14"		scope="compile"/>
		<dependency	groupId="javax.mail"			artifactId="mail"					 
version="1.3.2"		scope="compile"/>
		<dependency	groupId="javax.servlet"			artifactId="jsp-api"				 
version="2.0"		scope="provided"/>
		<dependency	groupId="javax.servlet"			artifactId="servlet-api"			 
version="2.4"		scope="provided"/>
		<dependency	groupId="struts"				artifactId="struts"					 
version="1.2.7"		scope="compile"/>
		<dependency	groupId="velocity"				artifactId="velocity-core"			 
version="1.4"		scope="compile"/>
		<dependency	groupId="velocity-tools"		artifactId="velocity-tools- 
generic"	version="1.1"		scope="compile"/>
		<dependency	groupId="com.verisign"			artifactId="verisign"				 
version="1.0"		scope="compile"/>
	</artifact:dependencies>	


I want to use that block for compiling and for building the WEB-INF  
directory. The problem is, I don't see how useScope can help. If I  
specify one useScope for compile time, that's one thing, but it's  
another when I go to copy those dependencies.

Of course I can make multiple copies of this tag and different  
useScope values, or make separate ones with just the right artifacts,  
but it seems to me that the scope attribute of the <dependency> tag  
is useless.

What's the intent of the useScope and scope attributes when used like  
this?

TIA,

-- 
Rick



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org