Uploaded image for project: 'Aries'
  1. Aries
  2. ARIES-1820

blueprint-maven-plugin should fail instead of silently and arbitrarily choose one of several beans with an identical ID

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

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

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            alien11689 Dominik Przybysz
            vorburger Michael Vorburger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment