You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Michael Vorburger (JIRA)" <ji...@apache.org> on 2018/07/24 15:10:00 UTC
[jira] [Created] (ARIES-1820) blueprint-maven-plugin should fail
instead of silently and arbitrarily choose one of several beans with an
identical ID
Michael Vorburger created ARIES-1820:
----------------------------------------
Summary: blueprint-maven-plugin should fail instead of silently and arbitrarily choose one of several beans with an identical ID
Key: ARIES-1820
URL: https://issues.apache.org/jira/browse/ARIES-1820
Project: Aries
Issue Type: Bug
Components: Blueprint
Reporter: Michael Vorburger
The blueprint-maven-plugin (1.4.0) will currently silently (!) pick one or another of two (or more) singleton annotated classes with the same name for the {{<bean>}} with an identical {{id=xyz}} to generate. This is VERY confusing... :P
This happened to us (in OpenDaylight) when we had a {{@Singleton class Something}} in {{package a;}} in one project, and another identically named singleton class in another package in another project which was a dependency of the first project (but both packages started with the same {{scanPath}} we use). But it probably even happens if you have two classes of the same name in different packages in the same project (not tested).
In an ideal world, such conflicts such lead to a build failure with a clear message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)