maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Tatam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MEJB-60) Optional classifer for ejb-client
Date Mon, 28 Dec 2015 20:12:50 GMT

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

Will Tatam commented on MEJB-60:
--------------------------------

How can i create a non-classified client using MEJB-92? Will 3.0 change the behaviour to create
non-classified clients by default and require users to swap to clientClassifier if they want
to use a classifier or does it only allow to create a *different* classifier than the main
artifact, but not one that as none at all?

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

Mime
View raw message