Hello,

I've built an IntelliJ/Maven integration plugin, which I'm going to publish (hopefully) tonight.

The plugin uses the Maven API directly for plugin and goal discovery, meaning that it does not spawn another Maven for it process - it is done inside the IntelliJ runtime, which makes it much faster (it still spawns a real process for goal execution though).

Now to my question: since it uses the Maven classes, it needs the Maven runtime JARs to be bundled along with it. From a legal stand point - what am I required to do to allow Maven to be distributed with it? Is bundling the Maven license file sufficient?

** Note that the plugin does not need to bundle the entire Maven distribution, only a small subset of its JAR files. **

For those interested in the plugin: it provides facilities for associating Maven POM files (project.xml) with IntelliJ modules, and specifying "favorite" goals for each module from the list of global goals (all this is done via the standard "Settings" dialogs of IntelliJ).

It provides an Ant-like panel on the right (just like the Ant plugin) which lists the project modules, and the favorite goals for each module, in addition to the goals defined in that module's maven.xml. Double clicking a goal (or selecting it and pressing "Play") will open on the bottom the maven execution console (just like the standard Run console) to show the output. If several maven processes are run simultaneously, a tab for each process is created of course.

In short, my emphasis was to make the maven integration closely resemble the standard intellij user interface, as if it is part of the tool (no strange looking GUI, etc).

If any of the maven dev team is interesting, I'll be more than happy to send the source code so it can become part of the standard Maven distro (or at least available from the maven site).

10x in advance,

   Arik.




Reply via email to