[jboss-jira] [JBoss JIRA] (WFLY-11442) Remove unused dependencies from org.jboss.as.ejb3
Ranabir Chakraborty (Jira)
issues at jboss.org
Thu Apr 2 03:23:37 EDT 2020
[ https://issues.redhat.com/browse/WFLY-11442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018190#comment-14018190 ]
Ranabir Chakraborty commented on WFLY-11442:
--------------------------------------------
Hello [~brian.stansberry] [~yersan], In the module.xml you just need to reference your jar file and any dependencies required. If you want the dependencies to be modules on their own then you need to explicitly declare them in your module.xml file.
I did a hit and trial with the listed dependencies. removed one and then build the module and wildlfy project. In this way, I removed the others also.
Then I run the smoke tests, by switching to the `testsuites` directory, fire the command: `mvn clean install -Dts.smoke .
When I saw everything got executed without any error then raised the PR.
> Remove unused dependencies from org.jboss.as.ejb3
> -------------------------------------------------
>
> Key: WFLY-11442
> URL: https://issues.redhat.com/browse/WFLY-11442
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Yeray Borges Santana
> Assignee: Ranabir Chakraborty
> Priority: Major
>
> Initial analisys checking only first level dependencies from the resource exposed by {{org.jboss.as.ejb3}} shows that these dependencies are being unused:
> * org.jboss.jts
> * org.wildfly.security.elytron-web.undertow-server
> * org.jboss.as.weld
> * org.wildfly.clustering.marshalling.spi
> * org.wildfly.clustering.marshalling.api
> * org.wildfly.client.config
> * org.hibernate
> The task here is verify that they are not used by any other machanism besides of being a first level dependency.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list