[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [m2e-users] custom packaging types as project dependencies
- From: Benjamin Bentmann <bentmann@xxxxxxxxxxxx>
- Date: Fri, 30 Mar 2012 14:18:56 +0200
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0
Stepan Vavra wrote:
For instance if I want to use axis soapmonitor:
Note, there's no <packaging> element within <dependency>, you likely
I don't see it in Maven's classpath container (i.e.
Whether a given dependency contributes to the classpath or not is
controlled by a component (artifact handler) looked up from the
dependency type. For custom dependency types, this component would have
to be provided via an extension plugin in your project.
For type=mar, I believe the axis2-mar-maven-plugin is responsible to
provide the artifact handler. Looking at its sources, I see
<addedToClasspath>false</addedToClasspath>, i.e. type=mar is
deliberately excluded from the classpath.
So m2e appears to do the right thing and should match what CLI mvn would
do during compilation etc.