More or less. You find more information about it in https://wiki.eclipse.org/M2E_compatible_maven_plugins#.3Cexecute.2F.3E_mapping. The SCR Mojo is indeed called from Eclipse. Maybe you can call that in IntelliJ directly? Konrad
> Am 23.04.2015 um 18:50 schrieb Andreas Schaefer Sr. <[email protected]>: > > Hi Konrad > > Thanks for the quick response. > > So Eclipse is running a “Maven Build” for a class whenever it is compiled? > > - Andy > > On Apr 23, 2015, at 1:55 AM, Konrad Windszus <[email protected]> wrote: >> >> Hi Andy, >> regarding 1) I am not aware of any existing effort to port this to IntelliJ. >> Regarding 2) there is the maven-scr-plugin which was made compatible with >> m2e (the Maven Eclipse Integration) in >> https://issues.apache.org/jira/browse/FELIX-3358. >> Basically Eclipse is executing a special maven goal whenever it triggers a >> compilation which will lead to the modification of the class file (i.e. the >> bind methods are being added). >> I am not aware though of a similar mechanism in IntelliJ though. >> Hope this information helps, >> Konrad >> >>> Am 23.04.2015 um 02:47 schrieb Andreas Schaefer Sr. <[email protected]>: >>> >>> Hi >>> >>> Ruben and I are working on a port of the AEM Sling Tooling for Eclipse to >>> IntelliJ. So I have a few questions: >>> >>> 1) Did anyone already try that? If so is the code available and for which >>> IntelliJ version? >>> >>> 2) Ran into some problems with the HotSwap of code deployed in Sling. It >>> turned out that 'maven-scr-plugin’ (I think) is generating bind and unbind >>> methods for @Reference which are not there with simple class compilation >>> and hence the HotSwap fails. Now Eclipse is working fine and I am wondering >>> if anyone knows what part of Eclipse or the Sling IDE Tooling is doing that. >>> >>> Cheers - Andy Schaefer >> >
