[
http://jira.codehaus.org/browse/MNBMODULE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick closed MNBMODULE-134.
---------------------------------
Resolution: Not A Bug
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
shows that you are misunderstanding import scope. It can only be used in
<dependencyManagement>. When you use it correctly, nbm-maven-plugin works with
it.
> Using aggregate pom does not include transitive dependencies
> ------------------------------------------------------------
>
> Key: MNBMODULE-134
> URL: http://jira.codehaus.org/browse/MNBMODULE-134
> Project: Maven NetBeans Module Plugin
> Issue Type: Bug
> Affects Versions: 3.4
> Reporter: Christopher Robin Elmersson
> Assignee: Jesse Glick
> Priority: Minor
> Attachments: MNBMODULE-134.zip, testcase-1-MNBMODULE-134.zip
>
>
> I have created an aggregate pom including various Jboss libraries needed to
> create a client communicating with a JBoss server.
> Including the pom like this:
> <dependency>
> <groupId>mygroup</groupId>
> <artifactId>jboss-client</artifactId>
> <version>1.0-SNAPSHOT</version>
> <type>pom</type>
> </dependency>
> the jar artifacts added as dependencies in the pom is not included in the
> list "Adding on module's Class-Path" and running the application yields class
> not found exceptions.
> Changing the packaging/type to jar, all dependencies are added and everything
> works as expected.
> Is this a bug or by design?
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
