[
http://jira.codehaus.org/browse/MNG-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4496.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
When you want to consume dependency types not defined by Maven itself, the
consuming project has to declare a build extension that defines this dependency
type and its characteristics. This build extension is usually the plugin that
produces the dependency type. See the [JBoss Packaging
Plugin|http://mojo.codehaus.org/jboss-packaging-maven-plugin/usage.html] for a
related example.
> SAR dependencies don't appear on the classpath
> ----------------------------------------------
>
> Key: MNG-4496
> URL: http://jira.codehaus.org/browse/MNG-4496
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.0.10, 2.2.1
> Environment: Windows XP SP3
> Reporter: Armin Wrobel
> Assignee: Benjamin Bentmann
>
> The problem, that SAR dependencies don't appear on the classpath existed
> already in Maven 1 and has been fixed for Maven 1.
> See https://svn.cargo.codehaus.org/browse/MAVEN-1304.
> I need to import a class file contained in a .sar file (JBoss service
> archive), but Maven 2.2.1 as well as 2.0.10 (and likely also those versions
> in between) don't find the class file during the compilation, because it
> isn't on the classpath, although it's correctly specified as a dependency:
> <dependency>
> <groupId>ch.hrms.casex</groupId>
> <artifactId>case-base-scheduling</artifactId>
> <version>${parent.version}</version>
> <type>sar</type>
> </dependency>
> During the compilation the error message: 'cannot find symbol...' is shown.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
