[jboss-jira] [JBoss JIRA] (WFLY-10829) Exclude ironjacamar-spec-api from the transitive depenencies
Yeray Borges (JIRA)
issues at jboss.org
Fri Aug 31 08:14:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627105#comment-13627105 ]
Yeray Borges edited comment on WFLY-10829 at 8/31/18 8:13 AM:
--------------------------------------------------------------
Sadly, it looks like I did not see this issue when I was working on WFLY-10918. {{ironjacamar-spec-api}} was excluded as a transitive dependency from {{ironjacamar-common-impl}} and {{ironjacamar-core-api}} but not from {{ironjacamar-core-impl}}
Even if the final solution to address this issue is to move the dependency scope in Iron Jamacar project to provider, at least for consistency, we should exclude {{ironjacamar-spec-api}} from {{ironjacamar-core-impl}} in Wildfly.
[~maeste][~gaol] Sorry for the mess, but if you agree with the above, maybe you can use this issue to add the pending exclusion in wildfly as well.
was (Author: yersan):
Sadly, it looks like I did not see this issue when I was working on WFLY-10918. {{ironjacamar-spec-api}} was excluded as a transitive dependency from {{ironjacamar-common-impl}} and {{ironjacamar-core-api}} but not from {{ironjacamar-core-impl}}
Even if the final solution to address this issue is to move the dependency scope in Iron Jamacar project to provider, at least for consistency, we should exclude {{ironjacamar-core-api}} from {{ironjacamar-core-impl}} in Wildfly.
[~maeste][~gaol] Sorry for the mess, but if you agree with the above, maybe you can use this issue to add the pending exclusion in wildfly as well.
> Exclude ironjacamar-spec-api from the transitive depenencies
> ------------------------------------------------------------
>
> Key: WFLY-10829
> URL: https://issues.jboss.org/browse/WFLY-10829
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Kabir Khan
> Assignee: Stefano Maestri
>
> Although not part of the server runtime, the ironjacamar-spec-api is included as a transitive dependency. This fixes it:
> {code}
> --- pom.xml
> +++ pom.xml
> @@ -4314,6 +4326,10 @@
> <version>\${version.org.jboss.ironjacamar}</version>
> <exclusions>
> <exclusion>
> + <artifactId>ironjacamar-spec-api</artifactId>
> + <groupId>org.jboss.ironjacamar</groupId>
> + </exclusion>
> + <exclusion>
> <artifactId>jbossxb</artifactId>
> <groupId>org.jboss</groupId>
> </exclusion>
> @@ -4346,6 +4362,10 @@
> <version>\${version.org.jboss.ironjacamar}</version>
> <exclusions>
> <exclusion>
> + <groupId>org.jboss.ironjacamar</groupId>
> + <artifactId>ironjacamar-spec-api</artifactId>
> + </exclusion>
> + <exclusion>
> <artifactId>jboss-integration</artifactId>
> <groupId>org.jboss.integration</groupId>
> </exclusion>
> @@ -4376,6 +4396,10 @@
> <version>\${version.org.jboss.ironjacamar}</version>
> <exclusions>
> <exclusion>
> + <groupId>org.jboss.ironjacamar</groupId>
> + <artifactId>ironjacamar-spec-api</artifactId>
> + </exclusion>
> + <exclusion>
> <artifactId>jboss-common-core</artifactId>
> <groupId>org.jboss</groupId>
> </exclusion>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list