[jbosstools-issues] [JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13322222#comment-13322222 ] 

Rob Stryker commented on JBIDE-22878:
-------------------------------------

I'm 100% not able to replicate this. I am able to replicate the UI showing simple-ejb-1.5.0.jar in a few places, but this is **only** in the UI. I am 100% unable to replicate, in either export or deploy, that the ejb's output name is simple-ejb-1.5.0.jar.   In all cases, both export and publish, I am seeing the actual result file is called simple-ejb.jar

[~mmalina] Can we go over this one together?

> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
>                 Key: JBIDE-22878
>                 URL: https://issues.jboss.org/browse/JBIDE-22878
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.3.Final, 4.4.0.Final
>         Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
>            Reporter: Mikhail Kalkov
>            Assignee: Rob Stryker
>             Fix For: 4.4.2.Final
>
>         Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing!



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)