Hello,
After I think about a year I’m about to start up another sling project. I’ve
used IntelliJ in the past for sling development, but now with IntelliJ 13.1 it
seems to be more picky on dependencies.
For example, in my parent pom I have:
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.scr</artifactId>
<version>1.8.2</version>
<scope>provided</scope>
</dependency>
And in my bundle pom:
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.scr.annotations</artifactId>
</dependency>
In the IntelliJ UI when looking at the pom.xml of the bundle the felix
dependency is highlighted in yellow with the message “Dependency is not OSGI
ready”, which is what IntelliJ has always done in the past.
However, when I try to use these annotations (Component, Service, Activate,
etc) I get compile errors in intelliJ:
“The package is not exported by the bundle dependencies”
In IntelliJ I can change this to a warning:
http://stackoverflow.com/questions/21465166/how-to-configure-osgi-in-intellij-when-its-handled-by-maven
Is this what you’ve done? Or is there another way around this?
Rob
