What's the meaning of addedToClasspath and includesDependencies when make own packaging type?

["sean chen(陈思淼)" <ch...@gmail.com>]

<component>
	<role>
		org.apache.maven.artifact.handler.ArtifactHandler
	</role>
	<role-hint>magma</role-hint>
	<implementation>
		org.apache.maven.artifact.handler.DefaultArtifactHandler
	</implementation>
	<configuration>
		<type>magma</type>
		<language>java</language>		<addedToClasspath>true</addedToClasspath>
                <includesDependencies >true</includesDependencies>

   	</configuration>
</component>

I think that may related to dependency manage when maven deal with the
self-define packaging type.

but who know the exact meaning of it?

Re: What's the meaning of addedToClasspath and includesDependencies when make own packaging type?

[Brett Porter <br...@apache.org>]

When used as a dependency type, something like the compiler plugin  
will add it to the classpath. If it's not meant to be used in that way  
(eg, WAR), it won't be.

- Brett

On 17/10/2008, at 3:02 AM, sean chen(陈思淼) wrote:

> <component>
> 	<role>
> 		org.apache.maven.artifact.handler.ArtifactHandler
> 	</role>
> 	<role-hint>magma</role-hint>
> 	<implementation>
> 		org.apache.maven.artifact.handler.DefaultArtifactHandler
> 	</implementation>
> 	<configuration>
> 		<type>magma</type>
> 		<language>java</language>		<addedToClasspath>true</addedToClasspath>
>                <includesDependencies >true</includesDependencies>
>
>   	</configuration>
> </component>
>
> I think that may related to dependency manage when maven deal with the
> self-define packaging type.
>
> but who know the exact meaning of it?

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


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