gshakhn/ideauidesigner-maven-plugin — pull request #1 by ggili (2013-06-12 23:19:04+00:00)
Title: Fixing class path build issue

Hi George,

I found out why this plugin is failing to build with my new changes to intellij-sonar-plugin.
Also I can easily reproduce the issue also with the existing intellij-sonar-plugin project (without my changes).

Currently in our pom.xml (intelliJ-plugin) we use compile scope for 'forms_rt', but in fact is not needed to be part of the deployment nor compile scope because comes with IntelliJ.

com.intellij
forms_rt
${idea.version}
compile

However if we put to 'provided' scope the ideauidesigner-maven-plugin will crash with some class not found exception which is in this jar.

What I did is I tweaked the class path building for ant. Every class path element must be included even the 'provided' ones (sure excluding the test scope ones).

My latest push to 'intellij-sonar-plugin' is failing because would require to change the scope for opeanapi.jar and idea-utils.jar from provided to compile. But having this fix is not require anymore.

I had to bump the jar version to grab every project dependency not just the 'compile' scope.

What do you think?