Craig P. Motlin

Wouldn't this be an asymmetry between the object/primitive APIs? I think the most consistent thing to do would be to call toArray(). On Iterables of unknown origin, that's one of...

> But that also means that you are not able to test the OSGi stuff with a local build. You need to do a release build, which you can not...

If folks do want to do OSGi testing manually, I could arrange the maven profiles slightly differently to make that happen. Rather than reuse the `release-artifacts` profile, I'd create a...

> What setup do you have? Which IDE? What steps do you perform to raise the issue you have? > > Maybe I can reproduce it somehow and find a...

> And why do you call `mvn clean install` and not just `mvn clean verify`? No reason, I think either one will reproduce the issue.

> Have you tried the verify approach? Just tried it now, same thing happens. While scrolling through the error messages to make sure they are identical, I realized there's another...

> To narrow down the issue, could you try to change the scope of the bnd annotations from provided to compile? Just to see if this changes anything. I tried...

@fipro78 thank you for the thorough investigation. I looked around in YouTrack for an IntelliJ bug like what we're seeing and couldn't find anything that matches exactly. The `build-helper-maven-plugin` config...

> Does this mean that the release steps need to be updated to trigger the profile? @nikhilnanivadekar, The way I structured this PR, I moved the plugin configuration of bnd-maven-plugin...

> You could try to do the `mvn install` only for the code generator plugin, which is needed to be installed. Then only call `mvn clean verify` to avoid that...