[jira] Commented: (MEJB-49) ejb-client: Transitive EJB Dependencies should be of type ejb-client

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MEJB-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235296#action_235296 ] 

Dennis Lundberg commented on MEJB-49:
-------------------------------------

I'm not sure I understand your request. This is the output I get when I run 'mvn dependency:tree' in the client module:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - testcase:testcase-client:jar:1.0.0-SNAPSHOT
[INFO]    task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree {execution: default-cli}]
[INFO] testcase:testcase-client:jar:1.0.0-SNAPSHOT
[INFO] \- testcase:testcase-ejb2:ejb-client:client:1.0.0-SNAPSHOT:compile
[INFO]    \- testcase:testcase-ejb1:ejb:1.0.0-SNAPSHOT:compile
[INFO] ------------------------------------------------------------------------
{noformat}

But the type of testcase-ejb1 (ejb) is to be expected, because thtat is what you specified in the POM of testcase-ejb2.

How is the plugin supposed to know that you want another type?

> ejb-client: Transitive EJB Dependencies should be of type ejb-client
> --------------------------------------------------------------------
>
>                 Key: MEJB-49
>                 URL: http://jira.codehaus.org/browse/MEJB-49
>             Project: Maven 2.x EJB Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2.1
>            Reporter: Roland Schneider
>         Attachments: ejb-testcase.zip
>
>
> When setting a dependency to an ejb-client jar that has dependencies to other ejb projects, these transitive dependencies are resolved as type ejb. It would be better when those transient dependencies would be referenced as ejb-client as well.
> I have not found any solution to this problem other than to manually exclude every single transient "ejb" dependency and instead add the ejb-client version of it directly. However this is cumbersome and error-prone for really complex projects.
> I have included a test-project-setup (no junit test) that demonstrates the described behavior. When you execute dependency:tree in the client project, you can see that the testcase-ejb1 dependency is of type "ejb".

-- 
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