You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2015/12/28 23:56:49 UTC

[jira] [Comment Edited] (MEJB-60) Optional classifer for ejb-client

    [ https://issues.apache.org/jira/browse/MEJB-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073233#comment-15073233 ] 

Karl Heinz Marbaise edited comment on MEJB-60 at 12/28/15 10:56 PM:
--------------------------------------------------------------------

If you like to ask question about the usage please use the users list with reference to this issue or any other issue...but don't use jira for that...BTW: This sounds like a feature request...


was (Author: khmarbaise):
If you like to ask question about the usage please use the users list with reference to this issue or any other issue...but don't use jira for that...

> Optional classifer for ejb-client
> ---------------------------------
>
>                 Key: MEJB-60
>                 URL: https://issues.apache.org/jira/browse/MEJB-60
>             Project: Maven EJB Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.3
>            Reporter: Will Tatam
>            Assignee: Karl Heinz Marbaise
>         Attachments: generateClassifiedClient.patch
>
>
> It is sometimes necessary to have an EJB jar which requires a classifier, but that does not automatically mean that you want your ejb-client to always have a classifier too and infact the current code has a comment next to the creation of the client stating
> "TODO: shouldn't need classifier"
> Patch attached created new config option called generateClassifiedClient which is true by default, to maintain previous behavour, but can be set to true in the configuration section of the pom to false should you wish to have a non-classified client



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)